head 1.35; access; symbols pkgsrc-2026Q2:1.35.0.26 pkgsrc-2026Q2-base:1.35 pkgsrc-2026Q1:1.35.0.24 pkgsrc-2026Q1-base:1.35 pkgsrc-2025Q4:1.35.0.22 pkgsrc-2025Q4-base:1.35 pkgsrc-2025Q3:1.35.0.20 pkgsrc-2025Q3-base:1.35 pkgsrc-2025Q2:1.35.0.18 pkgsrc-2025Q2-base:1.35 pkgsrc-2025Q1:1.35.0.16 pkgsrc-2025Q1-base:1.35 pkgsrc-2024Q4:1.35.0.14 pkgsrc-2024Q4-base:1.35 pkgsrc-2024Q3:1.35.0.12 pkgsrc-2024Q3-base:1.35 pkgsrc-2024Q2:1.35.0.10 pkgsrc-2024Q2-base:1.35 pkgsrc-2024Q1:1.35.0.8 pkgsrc-2024Q1-base:1.35 pkgsrc-2023Q4:1.35.0.6 pkgsrc-2023Q4-base:1.35 pkgsrc-2023Q3:1.35.0.4 pkgsrc-2023Q3-base:1.35 pkgsrc-2023Q2:1.35.0.2 pkgsrc-2023Q2-base:1.35 pkgsrc-2023Q1:1.34.0.2 pkgsrc-2023Q1-base:1.34 pkgsrc-2022Q4:1.33.0.2 pkgsrc-2022Q4-base:1.33 pkgsrc-2022Q3:1.31.0.8 pkgsrc-2022Q3-base:1.31 pkgsrc-2022Q2:1.31.0.6 pkgsrc-2022Q2-base:1.31 pkgsrc-2022Q1:1.31.0.4 pkgsrc-2022Q1-base:1.31 pkgsrc-2021Q4:1.31.0.2 pkgsrc-2021Q4-base:1.31 pkgsrc-2021Q3:1.28.0.2 pkgsrc-2021Q3-base:1.28 pkgsrc-2021Q2:1.27.0.6 pkgsrc-2021Q2-base:1.27 pkgsrc-2021Q1:1.27.0.4 pkgsrc-2021Q1-base:1.27 pkgsrc-2020Q4:1.27.0.2 pkgsrc-2020Q4-base:1.27 pkgsrc-2020Q3:1.25.0.2 pkgsrc-2020Q3-base:1.25 pkgsrc-2020Q2:1.23.0.2 pkgsrc-2020Q2-base:1.23 pkgsrc-2020Q1:1.20.0.2 pkgsrc-2020Q1-base:1.20 pkgsrc-2019Q4:1.18.0.4 pkgsrc-2019Q4-base:1.18 pkgsrc-2019Q3:1.15.0.6 pkgsrc-2019Q3-base:1.15 pkgsrc-2019Q2:1.15.0.4 pkgsrc-2019Q2-base:1.15 pkgsrc-2019Q1:1.15.0.2 pkgsrc-2019Q1-base:1.15 pkgsrc-2018Q4:1.14.0.2 pkgsrc-2018Q4-base:1.14 pkgsrc-2018Q3:1.13.0.26 pkgsrc-2018Q3-base:1.13 pkgsrc-2018Q2:1.13.0.24 pkgsrc-2018Q2-base:1.13 pkgsrc-2018Q1:1.13.0.22 pkgsrc-2018Q1-base:1.13 pkgsrc-2017Q4:1.13.0.20 pkgsrc-2017Q4-base:1.13 pkgsrc-2017Q3:1.13.0.18 pkgsrc-2017Q3-base:1.13 pkgsrc-2017Q2:1.13.0.14 pkgsrc-2017Q2-base:1.13 pkgsrc-2017Q1:1.13.0.12 pkgsrc-2017Q1-base:1.13 pkgsrc-2016Q4:1.13.0.10 pkgsrc-2016Q4-base:1.13 pkgsrc-2016Q3:1.13.0.8 pkgsrc-2016Q3-base:1.13 pkgsrc-2016Q2:1.13.0.6 pkgsrc-2016Q2-base:1.13 pkgsrc-2016Q1:1.13.0.4 pkgsrc-2016Q1-base:1.13 pkgsrc-2015Q4:1.13.0.2 pkgsrc-2015Q4-base:1.13 pkgsrc-2015Q3:1.12.0.30 pkgsrc-2015Q3-base:1.12 pkgsrc-2015Q2:1.12.0.28 pkgsrc-2015Q2-base:1.12 pkgsrc-2015Q1:1.12.0.26 pkgsrc-2015Q1-base:1.12 pkgsrc-2014Q4:1.12.0.24 pkgsrc-2014Q4-base:1.12 pkgsrc-2014Q3:1.12.0.22 pkgsrc-2014Q3-base:1.12 pkgsrc-2014Q2:1.12.0.20 pkgsrc-2014Q2-base:1.12 pkgsrc-2014Q1:1.12.0.18 pkgsrc-2014Q1-base:1.12 pkgsrc-2013Q4:1.12.0.16 pkgsrc-2013Q4-base:1.12 pkgsrc-2013Q3:1.12.0.14 pkgsrc-2013Q3-base:1.12 pkgsrc-2013Q2:1.12.0.12 pkgsrc-2013Q2-base:1.12 pkgsrc-2013Q1:1.12.0.10 pkgsrc-2013Q1-base:1.12 pkgsrc-2012Q4:1.12.0.8 pkgsrc-2012Q4-base:1.12 pkgsrc-2012Q3:1.12.0.6 pkgsrc-2012Q3-base:1.12 pkgsrc-2012Q2:1.12.0.4 pkgsrc-2012Q2-base:1.12 pkgsrc-2012Q1:1.12.0.2 pkgsrc-2012Q1-base:1.12 pkgsrc-2011Q4:1.11.0.8 pkgsrc-2011Q4-base:1.11 pkgsrc-2011Q3:1.11.0.6 pkgsrc-2011Q3-base:1.11 pkgsrc-2011Q2:1.11.0.4 pkgsrc-2011Q2-base:1.11 pkgsrc-2011Q1:1.11.0.2 pkgsrc-2011Q1-base:1.11 pkgsrc-2010Q4:1.10.0.4 pkgsrc-2010Q4-base:1.10 pkgsrc-2010Q3:1.10.0.2 pkgsrc-2010Q3-base:1.10 pkgsrc-2010Q2:1.9.0.22 pkgsrc-2010Q2-base:1.9 pkgsrc-2010Q1:1.9.0.20 pkgsrc-2010Q1-base:1.9 pkgsrc-2009Q4:1.9.0.18 pkgsrc-2009Q4-base:1.9 pkgsrc-2009Q3:1.9.0.16 pkgsrc-2009Q3-base:1.9 pkgsrc-2009Q2:1.9.0.14 pkgsrc-2009Q2-base:1.9 pkgsrc-2009Q1:1.9.0.12 pkgsrc-2009Q1-base:1.9 pkgsrc-2008Q4:1.9.0.10 pkgsrc-2008Q4-base:1.9 pkgsrc-2008Q3:1.9.0.8 pkgsrc-2008Q3-base:1.9 cube-native-xorg:1.9.0.6 cube-native-xorg-base:1.9 pkgsrc-2008Q2:1.9.0.4 pkgsrc-2008Q2-base:1.9 cwrapper:1.9.0.2 pkgsrc-2008Q1:1.8.0.4 pkgsrc-2008Q1-base:1.8 pkgsrc-2007Q4:1.8.0.2 pkgsrc-2007Q4-base:1.8 pkgsrc-2007Q3:1.7.0.22 pkgsrc-2007Q3-base:1.7 pkgsrc-2007Q2:1.7.0.20 pkgsrc-2007Q2-base:1.7 pkgsrc-2007Q1:1.7.0.18 pkgsrc-2007Q1-base:1.7 pkgsrc-2006Q4:1.7.0.16 pkgsrc-2006Q4-base:1.7 pkgsrc-2006Q3:1.7.0.14 pkgsrc-2006Q3-base:1.7 pkgsrc-2006Q2:1.7.0.12 pkgsrc-2006Q2-base:1.7 pkgsrc-2006Q1:1.7.0.10 pkgsrc-2006Q1-base:1.7 pkgsrc-2005Q4:1.7.0.8 pkgsrc-2005Q4-base:1.7 pkgsrc-2005Q3:1.7.0.6 pkgsrc-2005Q3-base:1.7 pkgsrc-2005Q2:1.7.0.4 pkgsrc-2005Q2-base:1.7 pkgsrc-2005Q1:1.7.0.2 pkgsrc-2005Q1-base:1.7 pkgsrc-2004Q4:1.6.0.6 pkgsrc-2004Q4-base:1.6 pkgsrc-2004Q3:1.6.0.4 pkgsrc-2004Q3-base:1.6 pkgsrc-2004Q2:1.6.0.2 pkgsrc-2004Q2-base:1.6 pkgsrc-2004Q1:1.5.0.4 pkgsrc-2004Q1-base:1.5 pkgsrc-2003Q4:1.5.0.2 pkgsrc-2003Q4-base:1.5 netbsd-1-6-1:1.4.0.2 netbsd-1-6-1-base:1.4 buildlink2-base:1.2 buildlink2:1.2.0.4 netbsd-1-6:1.2.0.6 netbsd-1-6-RELEASE-base:1.2 pkgviews:1.2.0.2 pkgviews-base:1.2 pkgsrc-base:1.1.1.1 TNF:1.1.1; locks; strict; comment @# @; 1.35 date 2023.04.21.13.14.19; author micha; state Exp; branches; next 1.34; commitid kNmY5FauXIDjCYlE; 1.34 date 2023.01.25.16.18.42; author micha; state Exp; branches; next 1.33; commitid 0zZuOEFb5gHZoWaE; 1.33 date 2022.10.31.13.44.16; author micha; state Exp; branches; next 1.32; commitid rO2mnaJv1I7tjSZD; 1.32 date 2022.09.30.15.33.45; author micha; state Exp; branches; next 1.31; commitid WBx2zXWDVWp2VTVD; 1.31 date 2021.11.19.10.58.46; author micha; state Exp; branches; next 1.30; commitid XXBNQ4nnYMswtohD; 1.30 date 2021.10.26.09.57.17; author nia; state Exp; branches; next 1.29; commitid 78VqYEUpimZYWieD; 1.29 date 2021.10.07.13.06.11; author nia; state Exp; branches; next 1.28; commitid th2tWmLhF9XPBSbD; 1.28 date 2021.08.06.10.04.43; author micha; state Exp; branches; next 1.27; commitid zhW3UOpXTRgLAT3D; 1.27 date 2020.11.25.15.40.16; author micha; state Exp; branches; next 1.26; commitid mK3bMIQSN7xIBhxC; 1.26 date 2020.10.23.16.23.40; author micha; state Exp; branches; next 1.25; commitid JgmRs4Tf2f9VU2tC; 1.25 date 2020.08.26.13.51.36; author micha; state Exp; branches; next 1.24; commitid RvBENPzEOx3oWzlC; 1.24 date 2020.07.17.10.58.41; author micha; state Exp; branches; next 1.23; commitid 25dT5ELfJlbAgqgC; 1.23 date 2020.06.05.17.04.31; author micha; state Exp; branches; next 1.22; commitid AVkcekySRL16E3bC; 1.22 date 2020.05.13.08.21.49; author micha; state Exp; branches; next 1.21; commitid jCn9ZR4ch1uju38C; 1.21 date 2020.05.11.14.07.49; author micha; state Exp; branches; next 1.20; commitid gYJXxzJSwDnEsP7C; 1.20 date 2020.03.04.11.35.10; author micha; state Exp; branches; next 1.19; commitid 863DPlpLYrzlO4ZB; 1.19 date 2020.01.10.12.24.56; author micha; state Exp; branches; next 1.18; commitid TxeMItGLeI4pN8SB; 1.18 date 2019.11.08.13.58.19; author micha; state Exp; branches; next 1.17; commitid JKSy6AcnWUiFm3KB; 1.17 date 2019.10.24.16.53.34; author micha; state Exp; branches; next 1.16; commitid uHQpq59poEnCO8IB; 1.16 date 2019.10.04.14.27.51; author micha; state Exp; branches; next 1.15; commitid 1hj8KTCNyZjsEyFB; 1.15 date 2019.03.19.14.21.20; author wiz; state Exp; branches; next 1.14; commitid SymjFQRGvw7Z0ZfB; 1.14 date 2018.11.10.19.55.54; author wiz; state Exp; branches; next 1.13; commitid 3IFRUrYhqbiA0rZA; 1.13 date 2015.11.03.00.56.26; author agc; state Exp; branches; next 1.12; commitid WnKX6A1NKZmI9AHy; 1.12 date 2012.01.30.03.43.58; author sbd; state Exp; branches; next 1.11; 1.11 date 2011.01.15.17.46.01; author tron; state Exp; branches; next 1.10; 1.10 date 2010.09.28.17.50.07; author tnn; state Exp; branches 1.10.4.1; next 1.9; 1.9 date 2008.06.08.02.40.38; author tonnerre; state Exp; branches; next 1.8; 1.8 date 2007.12.30.17.25.42; author cjep; state Exp; branches 1.8.4.1; next 1.7; 1.7 date 2005.02.23.14.45.26; author agc; state Exp; branches; next 1.6; 1.6 date 2004.05.02.22.26.12; author danw; state Exp; branches; next 1.5; 1.5 date 2003.02.23.11.28.59; author salo; state Exp; branches; next 1.4; 1.4 date 2002.12.16.23.21.06; author grant; state Exp; branches; next 1.3; 1.3 date 2002.09.25.06.35.48; author cjep; state Exp; branches; next 1.2; 1.2 date 2002.07.02.12.40.13; author wiz; state Exp; branches 1.2.4.1; next 1.1; 1.1 date 2002.06.26.13.37.01; author uebayasi; state Exp; branches 1.1.1.1; next ; 1.10.4.1 date 2011.01.16.20.55.53; author spz; state Exp; branches; next ; 1.8.4.1 date 2008.06.08.12.46.49; author tron; state Exp; branches; next ; 1.2.4.1 date 2002.07.02.12.40.13; author jlam; state dead; branches; next 1.2.4.2; 1.2.4.2 date 2002.08.21.22.42.03; author jlam; state Exp; branches; next ; 1.1.1.1 date 2002.06.26.13.37.01; author uebayasi; state Exp; branches; next ; desc @@ 1.35 log @archivers/star: Update to 1.7.0nb2 New features with AN-2023-04-19: - star: remove some C99-only code accidentally introduced in the previous release. - RULES/os-sunos5.def: the manstyle detection code for sunos5 and newer was broken for GNU make. Fix the code by moving the detection to a configure test setting the new make macro SOLARIS_MANSTYLE. Users building with other make implementations or those using the bootstrap smake were not affected. Reported by: Michael Bäuerle. Submitted by: Nico Sonack. - libschily: no longer provide the symbols fgetline, getline. libschily used to provide these symbols as alternative names for js_getline and js_fgetline for compatibility with UNOS. As their POSIX-incompatible signature causes problems when linking against musl statically, we now no longer provide these symbols by default. Users wishing to restore the old behaviour should remove -DNO_GETLINE_COMPAT from CPPOPTS when compiling libschily. - libschily: accordingly, the man pages getline(3) and fgetline(3) have been renamed to js_getline(3) and js_fgetline(3). - RULES: fix HCC_COM expansion when CCOM=clang. This fixes builds with GNU make when CCOM=clang. Submitted by: Nico Sonack. @ text @$NetBSD: distinfo,v 1.34 2023/01/25 16:18:42 micha Exp $ BLAKE2s (schilytools/2023-04-19.tar.gz) = 61bd4ce5c989eacd5ffffc8e6dd5435ba3594573c310405f2ff78bd52194b1e6 SHA512 (schilytools/2023-04-19.tar.gz) = 79e5d59ad84fefd32b689dc60db42cb522bfb2c544e7f5b8c2b85c3597c758519071ec043532d3e9e8b745bf4ff1ad32b4e1103eaac391282435e42a2ef94de5 Size (schilytools/2023-04-19.tar.gz) = 5896292 bytes @ 1.34 log @archivers/star: Update to 1.7.0 New features with AN-2023-01-12: UPDATING: - Solaris 11.4: man pages are now installed according to BSD conventions. Users may need to manually remove the following old man pages on update: streamarchive.4, makefiles.4, makerules.4, changeset.4, sccschangeset.4, sccsfile.4, and star.4. NEW FEATURES: - RULES/os-sunos5.def: man pages will now be installed into BSD-style sections on Solaris >=11.4 and descendents. - RULES: add symlink for arm64 OpenBSD - star: add support for configuring compression and decompression helpers. The command executed when a compression/decompression program is selected with the compress-program=name option can be configured using a new set of name_CMD=... options in /etc/default/star. Refer to the new COMPRESSION section in star(1) for details. This feature is currently not available on DOS (DJGPP). Submitted by Philipp Wellner. @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.33 2022/10/31 13:44:16 micha Exp $ d3 3 a5 3 BLAKE2s (schilytools/2023-01-12.tar.gz) = 14493310db8fe55fcb16f4b13cb6a4bb45ace541254c35e5b4d6d3fb178fc640 SHA512 (schilytools/2023-01-12.tar.gz) = a1eb37d5df8d2298ba4da6ccbf4bb937da13e8d9e4d7a8420b4d54a319c028c682e76a85c800d57a35d5f4b81a51b19600bbc2edb94641fa5e721ae23134ce15 Size (schilytools/2023-01-12.tar.gz) = 5895061 bytes @ 1.33 log @archivers/star: Update to 1.6.2nb1 Changelog from AN-2022-10-16: UPDATING: - Various man pages have been renamed to follow BSD conventions. Users may need to manually remove the following old man pages on update: streamarchive.4, makefiles.4, makerules.4, changeset.4, sccschangeset.4, sccsfile.4, and star.4. NEW FEATURES: - libfind/sfind: Fix incorrect error handling of -exec ... {} + primaries. Previously in some cases the primary returned an error even though it should always return true and in other cases it completely disregarded the exit code. Now the primary always returns true and sets the exit code of libfind and sfind to a non-zero value in case one of the commands returned with a non-zero exit code. Reported by Tavian Barnes. Submitted by Nico Sonack. - libfind/sfind: Report failures to query the password/group database for -nouser/-nogroup. Previously failure to query these databases was treated as if the user id/group id was not found. We now print a diagnostic message and return a non-zero value if the getpwuid() or getgrgid() call failed. Reported by Tavian Barnes. - libfind/sfind: Report presence of directory loops. Previously, such directory loops were silently ignored. Now, upon encountering a directory loop, sfind prints a diagnostic message to standard error. The search is continued but sfind will terminate with a nonzero exit status. This change improves compatibility with POSIX (cf. PASC interpretation request 1606). All libfind consumers calling the treewalk() function (mkisofs, sccs, and star) are affected. Reported by Tavian Barnes. Submitted by Nico Sonack. - star: rename tests/compress archives to avoid issues on case insensitive file systems. These file systems do not like having multiple files whose names only differ in letter case. Rename the archives to completely distinct file names to avoid this issue. Reported by tux . - *: With the switch of Solaris from SysV man page sections to BSD man page sections, man pages are now installed according to BSD conventions instead of SysV conventions. This affects the man pages makefiles(4), makerules(4), streamarchive(4), changeset(4), sccsfile(4), sccschangeset(4), and star(4). Reported by Friedhelm Mehnert. [pkgsrc note: Not yet, see Issue #40] - *: All references to Solaris man pages have been adjusted to BSD man page sections as used in Solaris 11.4. - libschily/getargs.3: document surprising behaviour that the the argument to a foo= parameter may be in the following argument. Thus, shell scripts should write foo= "$bar" instead of foo=$bar if $bar could possibly be empty. Submitted by Nico Sonack. - libschily/getargs.3: improve spelling and grammar. @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.32 2022/09/30 15:33:45 micha Exp $ d3 3 a5 3 BLAKE2s (schilytools/2022-10-16.tar.gz) = 7d1c3ba5c6db21be8dad6c0c79df0095c29d3a15b84241dc68ee75395cfda53c SHA512 (schilytools/2022-10-16.tar.gz) = c7c8a15807a06e2f51628d69982fa43e241e023de099c5d2e48975c9ac97c0f7d859e9c910e39ad718a03c13b5d39146122e7ef0ae22a4f9ef0484903738d4fa Size (schilytools/2022-10-16.tar.gz) = 5893336 bytes @ 1.32 log @archivers/star: Update to 1.6.2 Changelog from AN-2022-09-18: With great sadness we report the death of schilytools main author and long time maintainer Jörg Schilling (1955-03-27--2021-10-10). Jörg, we miss you! After his passing, development has been picked up by a group of volunteers who would like to keep the project alive and well. Our goal is to carefully preserve the portability and compatibility of this project while extending it to new platforms and implementing new tools and features that fit the tool set. As a part of the change in management, the schilytools project has moved from Sourceforge to Codeberg. - general: Explain how to contribute and update README - general: Add list of contributors - all: Misc spelling fixes Submitted by Friedhelm Mehnert. - all: Update E-Mail address and project URL in many places. Jörg's old joerg@@schily.net address is defunct and so is his postal address. As a part of an ongoing documentation cleanup, these addresses have been replaced by our new project pages in many locations. Submitted by Nico Sonack. - man pages: work around buggy syntax highlighting by adding \" " comments into various places. Submitted by Nico Sonack. - RULES: Fix build on macOS 12.4 - RULES: add i386-openbsd-clang.rul This should permit compilation on modern OpenBSD using clang as the system compiler. - autoconf: Work around clang bug in #pragma weak detection. A clang compiler bug causing a crash in the configure test for #pragma weak has been worked around, permitting use of weak symbols when compiling with clang. - star: convert star_fat.c generation to MKLINKS - star: fix wrong handling of pre-1970/post-2036 dates in gnutar archives on platforms with sizeof(time_t) > sizeof(long). - tests: fix arm64/aarch64 architecture confusion on OpenBSD Submitted by Nico Sonack. @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.31 2021/11/19 10:58:46 micha Exp $ d3 3 a5 3 BLAKE2s (schilytools/2022-09-18.tar.gz) = b081f23ec688681a17d035a6b0a684affe36f41aa1594934755ba2972c2850af SHA512 (schilytools/2022-09-18.tar.gz) = 48550db10e428b1430094a18bfad4781d1f6614eb5c273df7d579fff3e062a8d7ff8ff782c97e6929aaa9ad96b9d0c4f9fde62be0a3ae7fdd99c3f8336e24bde Size (schilytools/2022-09-18.tar.gz) = 5904117 bytes @ 1.31 log @archivers/star: Update to 1.6.1nb16 Rebase to the final Schily Tools release. The author Jörg Schilling passed away in October 2021. @ text @d1 1 a1 1 $NetBSD$ d3 3 a5 3 BLAKE2s (schily-2021-09-18.tar.bz2) = 1ee4b41d2f684e695d40cf03e4335ad0e699cbf0bb99b46e197e202d79ccc949 SHA512 (schily-2021-09-18.tar.bz2) = d25765074ac39ca2db63cb9841288dd4457f55588e0389a58ad78da62f745a766b4608d3d137a1908e2ca60511784d5f0af67bab1d1612478dbf120188ed5f31 Size (schily-2021-09-18.tar.bz2) = 4952788 bytes @ 1.30 log @archivers: Replace RMD160 checksums with BLAKE2s checksums All checksums have been double-checked against existing RMD160 and SHA512 hashes. @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.29 2021/10/07 13:06:11 nia Exp $ d3 3 a5 3 BLAKE2s (schily-2021-07-29.tar.bz2) = 19e70c3d4f724a51774a9e3d1eccfdcc79c7e0cee88a4f1df90aed24b2fc2830 SHA512 (schily-2021-07-29.tar.bz2) = 095740bf1190440d386145653763d74ad93abf996e6a1e56279b5441990898515356eda0f7b5d07386d2aac1ba1adf0e9dac423ce49ced4fdc13914857b6afc1 Size (schily-2021-07-29.tar.bz2) = 4927143 bytes @ 1.29 log @archivers: Remove SHA1 distfiles hashes @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.28 2021/08/06 10:04:43 micha Exp $ d3 1 a3 1 RMD160 (schily-2021-07-29.tar.bz2) = cde4b154b66cbb590faa32aae3448c62979e6c18 @ 1.28 log @archivers/start: Update to 1.6.1nb15 Changelog from AN-2021-07-29: - star: A single Linux xattr entry with a zero length value did disable all Linux xattrs for the related file. This is now handled correctly. Note that setfattr(1) on some Linux versions does not support to set empty xattr entries, but star on the same system can extract files with empty xattr entries. Thanks to a report from Dennis Katsonis - star: star -version now prints a new version date @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.27 2020/11/25 15:40:16 micha Exp $ a2 1 SHA1 (schily-2021-07-29.tar.bz2) = 6de3773faf2aa0418ac761c011736ea05c4a66a8 @ 1.27 log @star: Update to 1.6.1nb12 Changelog from AN-2020-11-04: - Makefile system: include/schily/nlsdefs.h no longer by default defines the macro __() because this is in conflict with definitions that are present in the system include files from newer HP-UX versions. Thanks to Rudi Blom for reporting. - star: The ACL support code and the Linux xattr code had a typo related to very long path names. As a result, ACLs and Linux xattrs did not work if the path name to a file was longer than PATH_MAX. Changelog from AN-2020-11-25: - Makefile System: Added support for MacOS on arm64 Thanks to a hint from Ryan Schmidt from macports Note that due to outstanding replies to recent changes in configure, it could up to now not be verified that all configure tests now work in a way that results in correct overall results. See below for an in depth report on the changes. - Makefile System: autoconf (config.guess & config.sub) now supports the new arm64 Apple systems. Thanks to Ryan Schmidt from macports for provinding the needed uname(1) output. - Makefile System: Added a new shell script "autoconf/uname" that helps to create shell scrips that allow to emulate an alien host system in order to test the correct behavior of configure.guess and configure.sub on the main development platform. This helps to adapt configure.guess and configure.sub to new platforms in the future. - Makefile System: The new clang compiler as published with the upcomming ARM macs has been preconfigured with -Werror -Wimplicit-function-declaration as the default behavior and thus is in conflict with the existing base assumption of the autoconf system that minimalistic C-code used for compile/link allows to check for the existence of a specific function in libc without a need to know which system #include file is used to define a prototype for that function. This clang version, as a result of this default, behaves like a C++ compiler and aborts if a function is used with no previous function prototype. This caused most of the existing autoconf test to fail with error messages about missing prototypes. We implemented a workaround using these methods for the identified problems: - Most of the exit() calls in the various main() functions have been replaced by return() to avoid a need to #include in special since these test may be the case for layered tests that #include files from the higher level parts. - Many autoconf tests programs now #include more system include files, e.g. stdlib.h and unistd.h to avoid missing prototype errors. This cannot reliably be done in tests that are used as a base for higher level tests where the high level test #includes own system include files, since older platforms do not support to #include the same file twice. So this is tricky... - A test for a Linux glibc bug caused by incorect #pragma weak usage inside glibc that prevents one or more functions from ecvt()/fcvt()/gcvt() from being usable outside glibc now uses hand-written prototypes for some of the libc interface functions in order to avoid using the system includes. If we did not do that, we could not use ecvt()/fcvt()/gcvt() on MacOS anymore. Thanks to Ryan Schmidt from macports for reporting and for the given help that was needed for remote debugging. Please send the needed feedback on whether the current state of the configure script results on correct autoconf results on the M1 Macs. @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.26 2020/10/23 16:23:40 micha Exp $ d3 4 a6 4 SHA1 (schily-2020-11-25.tar.bz2) = 9ca25eb2a0c3d583e5ca6ef11d1670f8a79914d5 RMD160 (schily-2020-11-25.tar.bz2) = 61d0aa46cc485e220ae46b95a1d318e899a8638c SHA512 (schily-2020-11-25.tar.bz2) = 6592e34eb53ef83b1b15e91ac65e5dace88ee62dba3d4b24b7e4b01b052e235b682ab87af266bceeab8a0be796e6105328975e88b12e37c541797ee9786bb01e Size (schily-2020-11-25.tar.bz2) = 4899985 bytes @ 1.26 log @archivers/star: Update to 1.6.1nb11 New features with AN-2020-09-04: - autoconf: congig.guess: FreeBSD on 64 bit ARM returns arm64 from uname -m; this was previously not supported and rejected by config.sub. We now convert "arm64" into "aarch64" in config.guess to get the usual expected results. - Makefile system: RULES/rules.env The environment variables FIGNORE, LD_LIBRARY_PATH LD_LIBRARY_PATH_32 and LD_LIBRARY_PATH_64 are now unexported from the enviroment. In special FIGNORE is dangerous, as it is frequently used by bash users but tells ksh93 to modify it's behavior with "echo *" and this may cause strange things with our makefiles in case that /bin/sh is ksh92. This applies e.g. to Oracle Solaris 11 and OpenSolaris. New features with AN-2020-10-09: - autoconf: Added support for newer HP-UX versions on Itanium. Thanks to Rudi Blom for reporting and making a change proposal. @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.25 2020/08/26 13:51:36 micha Exp $ d3 4 a6 4 SHA1 (schily-2020-10-09.tar.bz2) = e14d1dec1e476d40bd60ec35fa251ba45268ca8f RMD160 (schily-2020-10-09.tar.bz2) = 81ec46da6ef341f8a8340f389e96dbde2355d5af SHA512 (schily-2020-10-09.tar.bz2) = 3e64cb8d42749f1890e9f8e85de6571ec3f185f3c470078085494a52acb94018496d1b9a2a66b37091db55f08a7c4d4e8dc07cb40c3644aa76032bc7a2e2a74b Size (schily-2020-10-09.tar.bz2) = 4818571 bytes @ 1.25 log @archivers/star: Update to 1.6.1nb10 New features with AN-2020-07-18: - star: star could dump core if it was used as "star -t ..." or. "star -x ..." while being in a UTF-8 based locale and trying to deal with extremely long pathnames (more than PATH_MAX) in the archive. This bug was caused by the dummy conversion routines _to_utf8() or _from_utf8() that did not stop after "tolen" bytes (the current size of the dynamically growing path structure) have been copied. This bug has been introduced in 2018 when the dynamic path name variables have been introduced together with support for extremely long path names. - star: lpath_unix.c and lhash.c renamed a local variable buflen to bflen to avoid a gcc shadowing warning with the rest of star. - star: star.c fixed some fallthrough warnings from lint. - star: The FIFO code (which is 30 years old) did use an int for the size which historically was OK, but this did limit the size of the FIFO to 2 GB. Now with modern tape drives that are really fast, a FIFO with 2 GB would only give a tape streaming reserve for approx. 8 seconds, which is not sufficient. Approx. 30 seconds reserve are recommended. With modern tape drives, this would need approx. 8 GB of FIFO. Be. however careful not to use more than half of the real RAM available in the whole system for the star FIFO. Note that this change induced the need for a lot of derived changes in approx. 1000 lines of code spread over the whole star project and for this reason, it is advised to carefully test the new version and to report if problems occur. New features with AN-2020-08-12: - autoconf: added a new test for the existence of - autoconf: added new tests for Linux getauxval() and FreeBSD elf_aux_info() - libschily: getexecpath.c now uses getauxval() on Linux and elf_aux_info() on FreeBSD. This was needed since readlink("/proc/curproc/file") on FreeBSD returns random values for hardlinked files, making it impossible to use the result in order to find out which behavior variant of a fat binary is requested. - star: GNU cpio archives may contain longer path names than permitted by the AT&T documentation. This did cause problems with our automated recognition of swapped CPIO headers. We now use a more robust method. - star: GNU cpio archives may contain longer path names than permitted by the AT&T documentation. This could cause star to dump core because the cpio module did not yet call the routine to grow our new dynamic path store. - star: older GNU compilers seem to decide that a division: long long / long results in a long. We now cast the divisor to long long to definitely get the right result for a printf argument. - star: changed a name in a parameter list for lreadlink() to avoid a GCC shadow warning. - star: The variable use_fifo is also needed if the FIFO is not available (e.g. on DOS). The previous code did not compile on platforms that did not support to implement the FIFO. We moved extern BOOL use_fifo out of a #ifdef FIFO Thanks to a hint from Albert Wik. - star: The file README.otherbugs has been changed to match the state of today and a geocrawler based URL now includes an archive.org prefix as geocrawler no longer exists. @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.24 2020/07/17 10:58:41 micha Exp $ d3 4 a6 4 SHA1 (schily-2020-08-12.tar.bz2) = dbfff482d6c3f0cfbfaf3a43989cbf91f3e0402b RMD160 (schily-2020-08-12.tar.bz2) = 5e5f5e6ba8ba271c9b54e9eaf4eebf3e89b44dcf SHA512 (schily-2020-08-12.tar.bz2) = 2b86408107bcc0d928e9b3596be9da98f5e711df42b0d329f2bc91d35e191675ad3d297d8314ba2000ef6687f796b3115fd4de196da56314e7b5e452445ad3d3 Size (schily-2020-08-12.tar.bz2) = 4850267 bytes @ 1.24 log @archivers/star: Update to 1.6.1nb9 Changelog from AN-2020-07-01: - star: Backslashes are now honored when looking for the substitution separators in options like -s /from/to/ or -pax-s /from/to/ Previously, -s '/xxx\/yy//' was interpreted in a way that made the **to string** "yy" and the **from string** "xxx\" instead of making the from string "xxx\/yy" and the to string empty. @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.23 2020/06/05 17:04:31 micha Exp $ d3 4 a6 4 SHA1 (schily-2020-07-01.tar.bz2) = 7653c8b99d1aebe85337df681aae8ec1352c1ac1 RMD160 (schily-2020-07-01.tar.bz2) = 4c7989eb95cff9a4bdd5f521b95135902912ab8d SHA512 (schily-2020-07-01.tar.bz2) = 512f0c3488bde5812d2011b2c1b1f308b9c139331a16c40fc0b61983fd8ff26d60845ddc8adc4d5bf651405cde786e63de61a473a1c658d08e5a8fdf949312d6 Size (schily-2020-07-01.tar.bz2) = 4828878 bytes @ 1.23 log @archivers/star: Update to 1.6.1nb8 - Remove pkgsrc patches (merged upstream) - Move OS specific helper code to devel/smake/Makefile.common Changes from AN-2020-05-25: - libmdgest: Added a "defined(_M_ARM)" check for MSVC byte order definitions (byte_order.h). Thanks to "Excalibur" for reporting. - star: SmartOS supports aclutils.h as published include file (what we intented to include in Schillix-ON as well, since it is needed for libsec) and aclutils.h includes ctype.h. We thus need to #include before star.h in acl_unix.c The problem occurred because we did already have a aclutils.h related autoconf test, even though Schillix-ON does not yet ship aclutils.h Thanks to Michael Bäuerle from pkgsrc for reporting. - star: The subst command (since 2018) malloc()s the space for a copy of the old string in case that the string Is too long for the static storage. It did however still use the static buffer instead of a pointer to the allocated space. We now use the allocated space if needed. - star: The subst command for pax now supports the \1, \2, ... escapes for \(...\) selections in the from pattern, like it is used by sed(1). Thanks to Kristyna Streitova for reminding on this. - star: A new unit test for this new feature has been added, using the example from the SUSE bug-report for the above substitute command. - star: A new subst option -pax-s has been added that supports sed(1) like substitutions. The old option -s continues to support change(1) like substititions. NOTE: Both pax -s and star -pax-s silently fall back to change(1)-like substitutions in case that a target platform does not support "regex" in libc. @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.22 2020/05/13 08:21:49 micha Exp $ d3 4 a6 4 SHA1 (schily-2020-05-25.tar.bz2) = ba4f353ab3c3ecded4c417e8601f6986717508a9 RMD160 (schily-2020-05-25.tar.bz2) = 56f9a9812f26ff80699bb1e5ed299e24a724ff18 SHA512 (schily-2020-05-25.tar.bz2) = 73079c7c9c724911af10e641dfd82fb900c434c59a1d30fa34ac69f7f3e31dfe050cf718621574ce54cf5eb7189f32a5894fe070115c7eabc13c65e00b010b3b Size (schily-2020-05-25.tar.bz2) = 4794851 bytes @ 1.22 log @archivers/star: Add build fix for SmartOS The second patch silence a warning on NetBSD. @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.21 2020/05/11 14:07:49 micha Exp $ d3 4 a6 6 SHA1 (schily-2020-05-11.tar.bz2) = 1992e23344880fb58443c5b89b24fded4039f7a7 RMD160 (schily-2020-05-11.tar.bz2) = bdf3ac0349f00095d7e17f1b14a07f6dcb94a0e2 SHA512 (schily-2020-05-11.tar.bz2) = a12f0a3caa14c35af150afb4354fbe7c5b1d6ad301d24efbed6f0ec7c38919fe2bf863a117d46107178d11f60b9dd93f72f173c722e2e129d86d348b01fc56ee Size (schily-2020-05-11.tar.bz2) = 4783976 bytes SHA1 (patch-star_acl__unix.c) = 15d8fbf73af6646e19b0488cf3c0226f7b854332 SHA1 (patch-star_star.h) = 6ced8f4c2aac4fbcee4ea452e5d207e7b4bad064 @ 1.21 log @star: Update to 1.6.1nb6 Added SPECIAL_PERMS for config file (no more "wrong permissions" warning if installed as nonprivileged user. Changes from AN-2020-03-11: - configure: The autoconfiguration now has an enhanced test for waitid() that was needed since Mac OS is still not POSIX compliant and returns 0 instead of the signal number for a process that has been killed by a signal. MacOS did pass the POSIX certification as a result of a missing test for that problem. Since every vertified OS needs to run an annual refresh the certification with recent versions of the test, I guess that Mac OS (Catalina updates) may become more compliant witin a year. - psmake: The portable bootstrap compile environment for smake missed a symlink for unsetenv.c to libschily since the related code has been moved to libschily in 2018. This prevented compilation on IRIX. Thanks to Kazuo Kuroi for reporting - librmt: the code has been modified to allow librmt to be finally compiled without a need to link against libschily. This makes it easier to link ufsdump/ufsrestore from OpenSolaris against librmt. A call to errmsg() was replaced by a call to errmsgno() that has a private implementation in librmt already. - librmt: the man pages have been modified to make sure that man2html is able to correctly create links to referenced other man pages. - libstreamar: streamarchive.4 now mentions that the POSIX.1-2001 tar extensions are based on a Sun Microsystems proposal from 1997. - star: the man page now mentions that it is preferred to use the source from the schilytools instead of a star specific release. Changes from AN-2020-03-27: Changes from AN-2020-04-18: - librmt: A few small enhancements have been added to the man pages. This was a result of a code review for SchilliX-ON by Eric Ackermann - star: The unit tests port/lpath.sh did not work on IRIX because the "rm" command on IRIX is buggy and does not remove long path names (path names longer than PATH_MAX). We now use a recursive shell function to remove the long path. - star: The new shell function in port/lpath.sh did crash Linux in case that /bin/sh is "dash". "dash" is not POSIX compliant and fails to support arbitrary long working directory names. Whe therefore try to run the long path removal with "bosh", or at least "bash". Only if none of both is present, we fall back to the system default shell "/bin/sh". Changes from AN-2020-05-11: - Makefile system: A new version of the BSD make (bmake) program fixed a bug in pattern macro substitution, so we are now able to detect BSD make and to read BSD make program specific rules. This could in theory allow us to support BSD make in the future, but... Note that we on the other side discovered a new bug with pattern macro substitution in bsd make: The substitution: $(FOO:%=bar/%) is replaced by "bar/" with an empty "FOO", but of course, with an empty FOO, the substitution should be empty as well. This second bug (above) was fixed on May 6th, but we do not yet have all needed make rules and we do not know whether other bugs may still prevent the usability of BSD make. Supporting BSD make will be hard as BSD make does not support pattern matching default rules and this is important for placing the .o files into a sub-directory. Also note that the portable program source for "bmake" from "pkgsrc" is 2 years old and thus currently cannot be supported at all. If you like to experiment on your own, you need to get this version: http://crufty.net/help/sjg/bmake.html see http://www.crufty.net/ftp/pub/sjg/bmake.tar.gz and replace the newer files from the netbsd.org CVS tree by hand in order to fix the first and second mentioned pattern macro substitution bug. - Makefile system: RULES/MKLINKS was enhanced to create a new symlink RULES/r-bsdmake.tag that points to RULES/r-make.tag - Makefile system: The archive makefiles.tar.bz2 has been added to the schilytools tree to allow easy reuse of the makefile system for own projects. @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.20 2020/03/04 11:35:10 micha Exp $ d7 2 @ 1.20 log @star: Update to 1.6.1nb5 New features with AN-2020-02-11: - star: fixed typos in star.1 and star.4 Thanks to Eric Ackermann for reporting as a side effect of a code review for SchilliX-ON - star: fixed typos in header.c Thanks to Eric Ackermann for reporting - star: translated some German comment to English in diff.c, extract.c, list.c, remove.c, restore.c, fifo.c Thanks to Eric Ackermann for reporting as a side effect of a code review for SchilliX-ON - star: create.c: #ifdef __what_people_would_expect__ changed to: #ifdef __wrong_but_what_people_would_expect__ for better readability. - libschily: new man pages starthandlecond.3 and unhandlecond.3 - libschily: handlecond.3 and raisecond.3 now correctly mention handlecond() & raisecond() instead of handle()/raise(). The old names from 1980 had to be renamed because os an unfriendly actt from the C standard commitee. Thanks to Eric Ackermann for reporting as a side effect of a code review for SchilliX-ON - libschily: various small fixes in various man pages from libschily. Thanks to Eric Ackermann for reporting as a side effect of a code review for SchilliX-ON @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.19 2020/01/10 12:24:56 micha Exp $ d3 4 a6 4 SHA1 (schily-2020-02-11.tar.bz2) = da1dfe59c6b2a937b8dba2d4476db2ca8525a646 RMD160 (schily-2020-02-11.tar.bz2) = fe18d25ecdab9e2d7b587cce52cd745bd388ff6a SHA512 (schily-2020-02-11.tar.bz2) = 655a67cdc9387d79a077d44f11dacf2d5479da8b7bf4c59fb8a5fbf58ef23988f2a7aff23b3aec5ab7ac99541ea3439ddd55b53fc0e1d88efe601390161832c7 Size (schily-2020-02-11.tar.bz2) = 4360092 bytes @ 1.19 log @archivers/star: Update to 1.6.1nb4 Based on Schily Tools Release 2019-12-05. AN-2019-11-11: - libschily: the new functions wcastoi wcastol wcastolb that have been added with the previous release have been forgotten in the linker map file. - star: When using star -copy, the default is now -no-secure-links. This is what users like since they are copying their own data that per definition cannot be untrusted external data. - star: star -diff is now "more smooth" to use, when the archive type is GNU TAR and the "atime" or "ctime" properties are not present for a specific file. Before, Jan 1 1970 was the assumed time in the archive. - star: star -diff now prints a diff statistics summary. - star: New version date AN-2019-12-05: - include/schily/stdio.h: We no longer define getc_unlocked() on Solaris in case that it is defined already. This was needed since Oracle Solaris 11.4 compiles 64 bit by default and made stdio less opaque than before - this result in the same bahavior as for 32 bit programs. This means, we no longer need to use tricks to get fast access to stdio. Thanks to Rolf Dietze for reporting. - libschily: the function getargs() and similar (from the option parser group) fixed a bug that prevented the usability of the official method to include the char '+' inside option names by quoting the character in the option name used in the format string. This bug has been fixed in order to be able to support "star -dump+ ..." - libshedit: because of the changes in Oracle Solaris 11.4, we need to #undef FAST_GETC_PUTC in order to avoid to use getc_unlocked(). Thanks to Rolf Dietze for reporting. - libfind: A new function walksname() has been added to set up the internals in "struct WALK" for external path names. This feature is needed to support "star -c list=names -find ...". - libfind: The functions fetchdir()/dfetchdir(), sortdir(), cmpdir() now use size_t instead of int for the entry number count and the allocated size. This breaks binary compatibility in 64 bit mode for those users only, that use the interfaces fetchdir()/dfetchdir(), sortdir(), cmpdir(). The only application that currently uses these interfaces is "star". Simple users of libfind and programs compiled as 32 bit programs are not affected by the change. Warning: packetizers need to take care of the changed name of the shared library file for libfind. - libfind: Because of the binary incompatible change, we incremented the major library version number from 3 to 4. WARNING: This affects only distros that ship 64 bit versions of star using a shared version of libfind. Since Solaris defaults to 32 bit programs, this is expected to only affect Linux distros. - libstreamar: unicode.c has been changed to make sure that is works even in case that the "len" parameter is an unsigned. - libstreamar: to_utf8() from unicode.c has been rewritten to use size_t. instead of int. Several changes have been introduced in the other code as well. - libstreamar: from_utf8() from unicode.c has been rewritten to use size_t. instead of int. Several changes have been introduced in the other code as well. - star: The new-volume-script= script is now called at the end of _every tape_, even at the last one. This now allows to have a script that automatically renames a standard archive name into numbered archive names when a tree should be splitted into chunks, e.g. with this command line: star -c f=/tmp/v.tar tsize=1G new-volume-script='sh -c \ "mv /tmp/v.tar /tmp/v$(($1-1)).tar" nv' . you get partial archives named /tmp/v1.tar ... /tmp/vn.tar Note that this would not work in case that "sh" is the historical Bourne Shell, e.g. as seen on Solaris 10. This is because "shell arithmetics" is a feature that was not present in the historical Bourne Shell. - star: The man page now mentions that "star cli=tar ..." works as an alias to "star cli=suntar ...". - star: The man page now mentions that "star cli=gnutar ..." does not impement the bugs from the GNU option parser. - star: Is "star cli=xxx ..." is used, then star now calls set_progname(xxx) and thus prints error messages labelled with the command line interface name. - star: In "pax" command line mode, star now uses -no-fsync as default in order to behave the same way as the closed source Solaris pax does. - star: Star now allows to combine the option list=names with -find This is useful, whenever a list of filenames is longer than ARG_MAX and thus cannot be used in the star command line after -find. Here is an example on how to use the new feature in a mercurial. based development environment: (hg status -a; hg status -m; hg status -c) | sed -e 's/^. //' > .hgfiles star -c list=.hgfiles -find -mtime -100 > /tmp/new.tar The first command puts all files under control of mercurial into thw file ".hgfiles" , while omitting the compile results from the file ".hgfiles". The second command takes that list and puts only those files into the archive that have been modified during the past 100 days. - star: A new option "-dump+" allows to have the "SCHILY.volhdr.hostname" meta data field filled out even when not making dumps with an associated dump level. This helps to remember the origin of tar archives. - star: unicode.c has been changed to use the same comment as unicode.c in libstreamar. - star: unicode.c has been changed to make sure that is works even. in case that the "len" parameter is an unsigned. - star: to_utf8() from unicode.c has been rewritten to use size_t. instead of int. Several changes have been introduced in the other code as well. - star: from_utf8() from unicode.c has been rewritten to use size_t. instead of int. Several changes have been introduced in the other code as well. - star: due to the incompatible interface change in libfind (see above), several changes have been introduced in order to use size_t instead of int for fetchdir()/dfetchdir(), sortdir(), cmpdir(). This finally permits star to be able to make use of the current POSIX maximum meta data size for so called "pax" archives (TAR archives with POSIX.1-2001 meta data enhancements derived from the Solaris 7 concept for tar from 1997). Previous versions of star have been limited to data no longer than 2 GB (even though the star main code supports 8 GB file size), this version now supports 8 GB for the. sum of all meta data for a single file in case a 64 bit binary from star is used. - star: the fifo now has a new variant of te function runfifo() that is used by the new fifo(1) standalone program. See below. - star: The README now mentions the new "star cli= ..." method and the fact that star deals with infinite path name length. @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.18 2019/11/08 13:58:19 micha Exp $ d3 4 a6 4 SHA1 (schily-2019-12-05.tar.bz2) = cb7ea1133284955cba7023e2f0a296c53567743e RMD160 (schily-2019-12-05.tar.bz2) = 112011d7fa6f912802fc4458095dbf37d402dcb4 SHA512 (schily-2019-12-05.tar.bz2) = af16031fcc6345135d29d2dad2d30b85621e9959886843f393bf1ee51387bdbce9319e305bd58173c040995e1ce1c3325d34f9630712ccb618daa69470c249ef Size (schily-2019-12-05.tar.bz2) = 4360719 bytes @ 1.18 log @archivers/star: Update to 1.6.1nb3 Based on schilytools release from 2019-10-25. Changelog ========= - libstreamer: Added new keywords "fsdevmajor" and "fsdevminor" as there are too many incompatible st_dev binary formats. These keywords are not yet created, but they are understood. This permits to switch to the new format (fade out "dev") later. - star: Added new keywords "SCHILY.fsdevmajor" and "SCHILY.fsdevminor" as there are too many incompatible st_dev binary formats. These keywords are not yet created, but they are understood. This permits to switch to the new format (fade out "SCHILY.dev") later. - star: The amount of shared mamory used by default has been reduced to 1 MB on Ultrix. These are old small machines, that do not support 8 MB. @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.17 2019/10/24 16:53:34 micha Exp $ d3 4 a6 4 SHA1 (schily-2019-10-25.tar.bz2) = 2e32420f66700db63973414ba3b8cd1d1c4ba718 RMD160 (schily-2019-10-25.tar.bz2) = 17d5542ec62165dacf7a82e5bba8335f16508de0 SHA512 (schily-2019-10-25.tar.bz2) = c2f98bee65dc4c49a06f9a5795e11e17754c2869a18fc046d134ce83461fe3598ada1eae471a6b171542adddf2931d4d6e32b1d627a28f897e5e3dcc34b25149 Size (schily-2019-10-25.tar.bz2) = 4412486 bytes @ 1.17 log @archivers/star: Update to 1.6.1nb2 Based on Release 2019-10-07. Changelog ========= - configure: Some shells report a syntax error with "< file (cmd)" and need the redirection statement to be *after* the command. Our changes to support the V7 shell by adding round braces caused ash variants like "dash" to fail. Thanks to Harald van Dijk for reporting - cont/cc-config.sh: canged some :>some-file statements into (:)>some-file. they have meen missed when introducing work arounds for the V7 Shell on Ultrix that does not support I/O redirection for builtin commands. Thanks to Robert Clausecker for reporting - libschily/resolvepath.c: resolving a symlink that points to another symlink that points to itself, caused a coredump as a result from an endless recursion. We now detect this situation and abort the check before the endless recursion causes a stack overflow. A symlink that directly loops is immediately stopped. A longer symlink loop chain over more than one symlink can only be detected by the recursion nesting level and is aborted after a nesting level of 1024 has been reached. This works under the assumption that the minimum stack size is more than 1024 * PATH_MAX and that there is no useful directory path with more than 1024 symlinks in the path. ----> This problem affected star and SCCS. Thanks to Philipp Wellner for reporting - star: Added a hint to the man page that helps to find pkglist= as a. similar option to list= - star: The new method to avoid extracting symlinks that point outside the star working directory that has been introduced in October 2018 could cause a core dump if a symlink is checked that points to another aready existing symlink that points to itself. This was caused by a problem in libschily/resolvepath.c, see above. Thanks to Philipp Wellner for reporting - star: The option -no-secure-links now may be configured as a global default via the tag STAR_SECURE_LINKS= in the file /etc/default/star and as a private default via an environment of the same name. If the value for this tag is 'n' or 'N', -no-secure-links is made the default, any other value sets the option -secure-links as the default. This may be useful for sysadmins that frequently use star to copy installation specific files, but it is risky in case that alien TAR archives are imported. The good news is that this permits users to switch to the old star behavior where no checks for risky links existed. Thanks to Dennis Clarke for reporting - star: A new enviroment STAR_NOHINT has been introduced to supress hint messages that are otherwise seen in case STAR_SECURE_LINKS or STAR_FSYNC is in the environment or in /etc/default/star - star: New version date @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.16 2019/10/04 14:27:51 micha Exp $ d3 4 a6 4 SHA1 (schily-2019-10-07.tar.bz2) = d9d901bb737bdeb3242aee92259955d7da17e684 RMD160 (schily-2019-10-07.tar.bz2) = 23c47c0e0d85ce051cb9946718fc6bb87de6977c SHA512 (schily-2019-10-07.tar.bz2) = 9d2ce93c104c1027fe96371929b7f78351248b2c73200b7762c7ce5b38ba680f0e8dae7d90d5ce83184a77a5d378890361f4b5c57383f601d0f11aafae5e430f Size (schily-2019-10-07.tar.bz2) = 4404621 bytes @ 1.16 log @star: Update to 1.6.1nb1 Switch to latest distfile. Update PLIST. Replaced MESSAGE with share/doc/star/INSTALL.pkgsrc. Changelog ========= Release 2019-03-29: - libschily: the lutimens() emulation no longer returns ENOSYS in case that the lstat() call fails, since this error code may e.g. be ENAMETOOLONG and used as an important indicator for long path name handling. This bug caused incorrect behavior when star extracted long pathnames on a platform without utimensat(). - star: The code restructuring to openat() from Summer 2018 did not only cause a noticeable speed up even when not using -find, it at the same time resulted in a wrong error message when a file type was seen that is not archivable (e.g. a socket while using the USTAR format). The correct message was something like "Unsupported filetype", while the bug caused a "file not found " message. This has been fixed by adding a new parameter "fd" to the function stat_to_info(). - star: header.c::get_xhtype() we did forgot to initialize: finfo.f_devminorbits and finfo.f_xflags This is now done. - star: The USTAR format now is able to create base-256 values in the field "t_devmajor". "t_devminor" did already support base-256. - star: The GNU tar format now is able to create base-256 values in the fields "t_devmajor" and "t_devminor". - star: The man page star.4 now mentions which fileds may have base-256 numbers. - star: The man page star.4 now longer contains the doubled "field field" in the explanation of the added UID/GID number for ACLs. - star: The man page star.4 now has a better description for the additional numeric fields in the ACL entries to prevent GNU tar from continuing with it's incompatible ACL implementation. - star: New ACL reference archives for the ultra compact format, that has been defined together with the libachive people, have been added to the directory testscripts/: acl-nfsv4-compact-test.tar.gz acl-nfsv4-compact-test2.tar.gz acl-nfsv4-compact-test3.tar.gz acl-nfsv4-compact-test4.tar.gz acl-nfsv4-compact-test5.tar.gz - star: Linux now uses the new instead of to retrieve file flags. Thanks to a hint from Martin Matuska from the libarchive team. - star: Support for the following new BSD Flags: compressed hidden offline rdonly reparse sparse system has been added. Thanks to a hint from Martin Matuska from the libarchive team. - star: Support for the following new Linux flags: dirsync nocow notail projinherit topdir has been added. Thanks to a hint from Martin Matuska from the libarchive team. - star: Support for reading non-comliant libarchive tarballs that use. "securedeletion" or "journal" instead of the documented text has been added. This was used by libarchive until March 20, when libarchive has been fixed. We introduce the above names for compatibility with old TARs created by libarchive. - star: When an "old star" archive is read and this archive is from a system like FreeBSD with non-continous minor bits, star no longer warns unless there is a device file in the archive. - star: unit tests: the scripts now contain LC_ALL=C export LC_ALL instead of just LC_ALL=C to make the environment exported. - star/libstrar: The case where iconv() returns -1 and sets errno to E2BIG is now handled correctly. - star: The testscripts/ directory now contains the tar test archives from the portability tests from Michal Gorny. Check http://cdrtools.sourceforge.net/private/portability-of-tar-features.html for an updated (to match star-1.6) variant of the results from the portability tests from Michal Gorny. - star: older versions of star did not print the messages: "WARNING: Archive is 'xxx' compressed, trying to use the -xxx option.\n" in case that the option -print-artype was in use. Later versions that added support for more than "gzip" and "bzip2" forgot to add the same exception for the new compression methods. We now ommit this message for all compression types. - star: Support for the "lzma" compression has been added. - star: Support for the "freeze2" compression has been added. - star: The compression method name list did not include the text "zstd". We added the missing text. - star: The hint messages that are printed when a compressed input archive is not seekable did forgot to mention "lzip" and "zstd". We added the forgotten messages. - star: New unit tests check whether star is able to auto-detect and auto decompress various compression formats. - star: The unit tests now include the portability tests from Michal Gorny - A new option cli=name (must be argv[1]) allows to select all supported command line interfaces (star, suntar, gnutar, pax, cpio) when called as star. This is needed to be able to test all command line interfaces from out unit tests since star is not installed in this case and a selection from argv[0] would not work. - star: The version date is now "2019/03/20" Release 2019-04-29: - libfind/star: the verbose listing code has ben restructured to have the file permissions in the same string as the file type. This is needed to implement the POSIX pax listformat interpreter format %M in future. - libfind/star: the verbose listing no longer prints "l" for mandatory record locking for non-directory type file, but rather only for plain files. - star: The "gnutar" emulation now prints the --help output to stdout as GNU tar does. - star: The gnutar.1 man page now mentions that the GNU tar options -g / -G did never work and it thus makes no sense to implement them. - star: very outdated code in list.c has been removed. - star: Added new unit tests for incremental backups and restores. This in special include tests that always fail with GNU tar as GNU tar is not usable and never was usable for incremental restores in case that the differences are more than trivial. - star: new version date 2019-04-01 Release 2019-06-13: - star: fixed a bug in the FIFO code that mainly happened on Linux (with a 1000x higher probability than it happens on Solaris). The bug was. caused, as a check for a flag has been done twice instead of only once where it could change it's value between both locations. As a. result, star reported "star: Implementation botch: with FIFO_MEOF" as the tar side of the FIFO did sometimes not wait for the FIFO_IWAIT state when called as "star -multivolume -tv f=... f=... ... For this reason, star incorrectly got a wakeup at the wrong location. The bug appeared in case that star -x/-t -multivol f=.. f=.. .... has been called with very small tar archives. Thanks to Heiko Eissfeldt for reporting. - star: The FIFO code renamed the "flag" member of the "m_head" structure to "gflag" for better readability. - star: The debugging code in the FIFO has been enhanced to print the names of the flag bits in addition to the hex values. - star: A deadlock situation that happens once every 500000 tries on Linux with multi-volume archives has been fixed. The problem was caused by a complex condition where the get side of the FIFO needs to check the EOF FIFO flag and the amount of data available in the FIFO and then decide whether to wait for a wakeup or not. Since the EOF flag needs to be checked first, a context switch in the get side of the FIFO could allow the put side to set the EOF flag before the get side did check the fill ratio of the FIFO. This caused both the get side and the put side to wait for a wakeup. The new code introduced a new variable mp->mayoblock that is set by the get side before checking for EOF. This new flags allows the put side to know that the get side is just in a critical situation and lets the put side wait until mp->mayoblock is no longer set, which signals a stable state in the get side. This permits to avoid the deadlock. - star: Note that the FIFO has been initially written as a lock free design in the late 1980's. This is to allow high portability to even older UNIX versions. The star FIFO works on all UNIX variants that support pipes and shared memory, which is e.g. the case for SunOS-4.0 from 1988. At the time the FIFO has been designed, the target OS did not support multi-CPU systems and problems in the FIFO first appeared with massively faster multi-CPU systems around y2000. The recently detected problems all have been triggered by a different context switch behavior on Linux, even though they could have appeared on any OS in case that many million tries are attempted. - star: bumped version to 1.6.1 Release 2019-07-15: - star: the compress unit test no longer fails on Cygwin because the gzip binary is compiled incorrectly and does not support LZW. The related test is now skipped. Thanks to Heiko Eissfeldt for reporting - star: some new unit tests failed if the schilytools source tree has been installed in a directory with spaces in it's name. Thanks to Heiko Eissfeldt for reporting - star: The unit tests for incremental backups include archives that include userid/groupid and username/groupname that may not be restorable on a different computer. We now ignore these ID meta. data when comparing the results. Thanks to Heiko Eissfeldt for reporting - star: When comparing nanoseconds in time stamps, star now has a mode that treats time stamps as equal in case that tv_nsec % 100 == 0 and the rest of the nano seconds is equal. This is needd on Cygwin since NTFS counts in 1/10 microseconds since Januar 1 1601. This applies to both star -diff and the "newer" check while extracting files. Thanks to Heiko Eissfeldt for reporting - star: a new option diffopts=dnlink has been implemented to support filesystems that do not follow the historic UNIX model for hard links on directories. Since Cygwin usually has a linkcount of 1 on directories, you need to use "star -diff diffopts=!dnlink ..." if you like to diff the meta data from a historical UNIX filesystem. Thanks to Heiko Eissfeldt for reporting - star: The incremental backup/restore tests now use. "star -diff diffopts=!dnlink ..." to make them work on Cygwin. Thanks to Heiko Eissfeldt for reporting - star: star -c -H exustar -acl -xattr-linux . did cause file not found messages from the attempt to archive the Linux xattrs. This was caused by a change from July 2018 when trying to optimize directory access in (non-find) create mode. The call to read the Linux xattrs has now been moved to the location where in former times the ACL code has already been moved. The move is needed because there is no ACL/XATTR related function that is similar to openat(). - star: A similar problem with get_xattr() did exist with star -diff - star: star -diff did not compare ACLs since getinfo() no longer includes a call to get_acl(). We now call get_xattr() and get_acl() in diff.c - star: The Solaris ACL interface now implelements lacl() / lacl_get() / lacl_set() to support very long pathnames with ACLs. - star: The Linux ACL interface now implelements lacl_get_file() / lacl_set_file() to support very long pathnames with ACLs on platforms that implement the withdrawn POSIX ACL draft. - star: The Linux xattr interface now implelements. llgetxattr() / llsetxattr() / lllistxattr() to support very long pathnames with Linux xattrs. - star: New version date Release 2019-07-22: - star: "pax -pe" no longer sets the variable "doxattr" as this caused an error message: "NFSv4 extended attribute files are not yet supported.\n" that caused the OpenSolaris-ON "nightly" compilation to abort as a result of that error and exit code != 0. Release 2019-08-13: - libschily: Various functions and *at() emulation functions call stat() even though the caller does not know about that call. This could cause a missbehavior in case that a file returns EOVERFLOW with a normal stat(). We now compile these functions in unconditional large file mode to overcome that problem. The affected files are: diropen.c lutimens.c findinpath.c linkat.c mkdirs.c searchinpath.c resolvepath.c lchmod.c renameat.c. Note that this problem affected star(1) on platforms that do not fully implement all *at() interfaces, since star started to support really long path names in July 2018. - star: Star did not compile on platforms without ACLs anymore since we did rearrange the code with schilytools 2019-07-15. We now have the needed #undef USE_ACL in diff.c as well. Thanks to Dennis Clarke for reporting. - star: Avoid a warning when a star -dump archive is unpacked on FreeBSD or Linux with non-contiguous minor bits. The warning is not needed since we only use SCHILY.dev in order to detect mount points but not to compute the major/minor parts. Release 2019-08-13: - star: star -xdev -find typically works to exclude mounted files. It still does not always do what is expected, e.g. in case that /proc is in the tree of scanned files, where files deep in the new mounted tree suddenly have the same FS ID as other filesystems, e.g. the file /proc//path/a.out. In such cases, "star -find -xdev" is still recommended where the mounted file exclusion is done inside libfind instead of being done inside star. Before, files on other filesystems have not been honored at all when using "star -xdev -find ...". @ text @d1 1 a1 1 $NetBSD$ d3 4 a6 4 SHA1 (schily-2019-09-22.tar.bz2) = 5ab0f574cca9f89a225948b3df2918fccc7f06e2 RMD160 (schily-2019-09-22.tar.bz2) = 70fb7b2b66e85cac7cd94bb6ef92b5ed1cdce2c0 SHA512 (schily-2019-09-22.tar.bz2) = 83eecb7644ca720a3b1cae69481202a83ff8bf602bf6c0f8bab96f58402adc53fe142802c0d725c63f5109ec4875d99e8f93842fed7efa77d3e23c5cfc97d9e3 Size (schily-2019-09-22.tar.bz2) = 4460891 bytes @ 1.15 log @star: update to 1.6. Update provided by Michael Bäuerle via pkgsrc-wip. Changelog ========= Release 2018-11-22: -libschily: resolvenpath() did not work as expected when some path names do not exist. A stat() call that should check whether we already reached the "/" directory caused a return (-1) even with (flags & RSPF_EXIST) == 0 This bug caused star to classify more symlinks as dangerous than needed. - star: A typo in the function dolchmodat() has been fixed. The bug has been introduced in July 2018 while adding support for very long path names. - star: added a new timestamp to the star version. - star: The man page now mentions incremental backups and restores in the FEATURES section. Release 2018-12-06: - star: hole.c: A memory leak in in hole.c::put_sparse() has been fixed. Thanks to Pavel Raiskup for reporting this coverity result. - star: xheader.c: the macro scopy() no longer has a semicolon at the end. Thanks to Pavel Raiskup for reporting this coverity result. Release 2019-01-22: - libstrar & star unicode.c: iconv() may return > 0 if there are characters that could not be converted into an identical meaning. We therefore now check for ret != 0 instead of ret == -1. - star: added support for auto detection of "zstd" compressed archives. - star: added a new option -zstd to support compression and uncompression using the program "zstd". - star: Recently, star did hang in the FIFO code on Solaris. This did not happen on Solaris over 20 years before... On Linux - on fast multi CPU machines - the probability that a child process from fork() starts up before the parent is 1000x higher than on Solaris, where 10 million tries were needed to reproduce the same problem. As a result, the FIFO in star on Linux could in rare cases (1 of. ~ 10000 tries) even finish the 1st read() from the input file before the "tar"-process starts with e.g. command lines like "star -tv" or. "star -x". Since star introduced auto-byte-order detection and handling in 1985, star needs a special start up sequence to do that. Star introduced the FIFO in the late 1980s and the machines from that time did always restart the parent before the fork()ed child starts. The new OS behavior thus caused a situation that was not forseeable when the FIFO has been designed. This new OS behavior caused a deadlock in aprox. 1 of 10000 star calls on Linux and 1 of 10000000 star calls on Solaris. Star now waits when entering the FIFO fill-process until the. FIFO get-process did start up before trying to wake up a waiting get process. - star: On Linux, in 1 of 1.5 million tries, star did die from SIGPIPE. Note that this did never happen on Solaris. Star now ignores SIGPIPE and it seems that this fixed the problem since it did not happen again after that change with even 100 million tries. - star: The debug printing for the FIFO has been enhanced to print more information from the FIFO control structure to make it easier to debug problems like the ones mentioned above. - star: There seems to be a problem in pipe handling in the Linux kernel. It seems that in rare cases, the read(2) on a pipe returns 0 even though the write side did write(2) one byte to the pipe just before calling exit(). Unfortunately, this problem is hard to debug as it happens only once every ~30 million tries. Our workaround is to behave as if the expected byte could be read and star currently prints something like: star: Erfolg. Sync pipe read error pid 8141 ret 0 star: Erfolg. Ib 0 Ob 1 e 0 p 1 g 0 chan 5. star: Erfolg. Trying to work around Kernel Pipe botch. before it continues. Since the star exit code in such a case is 0, we assume that this is a correct workaround and this case thus may be made completely silent in the future. - star: an even less frequent FIFO problem (occurs once every 50 million tries on fast multi CPU machines) has been identified. Star reports a hard EOF on input even though the complete file with logical EOF has been read and there is still input to process. In order to debug this problem a debug message has been added to the code. With this debug message, it turned out, that this problem happened because a context switch occurred in the FIFO read process after it did see an empty FIFO and later, after the process was resumed, the following check for the FIFO_MEOF flag did see EOF. We now first check for the FIFO_MEOF flag and later for the amount of data inside as the FIFO as FIFO_MEOF is set after the FIFO content has been updated and thus a context switch is no longer able to cause a wrong assumption about the content of the FIFO. If you still see this, please send a report. - star: added support to print debug malloc statistics to better debug memory problems in star. - star: pathname.c:: free_pspace() now only frees the path buffer if it is != NULL - star: fixed a bug in the file create.c that caused star to incorrectly grow the path buffer by 2 bytes for every archived file. This caused star to constantly grow if a larger amount of files are archived and eat up all memory available to 32 bit processes if the archived filesystem is larger than approx. 1 TB. - star: If the path name now cannot be handled because of low memory, we print a warning that includes the text "out of memory". - star: Now checking whether open of /dev/null failed while running a compress pipe. This avoids a core dump on defective OS installations. Thanks to Pavel Raiskup for poiting to a related Coverity message. - star: props.c: Added a missing /* FALLTHROUGH */ comment.. Thanks to Pavel Raiskup for poiting to a related Coverity message. - star: create.c: Add more comment for the CPIO CRC format handler to explain why the last instance if a series of hard links for a file needs to archive the data. - star: diff.c: added a filling fillbytes(&finfo, ...) to make sure that ACL pointers are initialized. Thanks to Pavel Raiskup for poiting to a related Coverity message. - star: Several /* NOTREACHED */ comments have been added to tell programs like coverity that after a NULL pointer check, there is no continuation of the program Thanks to Pavel Raiskup for poiting to a related Coverity message. - star: extract.c: A if (path->ps_path == '\0') has been corrected to if (path->ps_path[0] == '\0') after a mktemp() call. This was a typo introduced with the new support for extremely long path names. Thanks to Pavel Raiskup for poiting to a related Coverity message. - star: extract.c An initalization for a struct pathstore has been moved to the front to verify that path.ps_path is always initialized. Thanks to Pavel Raiskup for poiting to a related Coverity message. - star: header.c: isgnumagic(&ptb->dbuf.t_vers) has been changed to isgnumagic(ptb->ustar_dbuf.t_magic) as it is a "ustar" structure that is going to be checked. Thanks to Pavel Raiskup for poiting to a related Coverity message. - star: some Cstyle changes - bsh / Bourne Shell / star: the function hop_dirs() no longer checks for p2 != NULL before calling *p2 = '/' as p2 has been granted to be != NULL from a break with strchr(p, '/') == NULL Release 2019-02-18: - star: another similar has been fixed similat to what has been fixed already in the 2019-01-22 release: An even less frequent FIFO problem (occurs once every 50 million tries on fast multi CPU machines) has been identified. Star reports a hard EOF on input even though the complete file with logical EOF has been read and there is still input to process. In order to debug this problem a debug message has been added to the code. With this debug message, it turned out, that this problem happened because a context switch occurred in the FIFO read process after it did see an empty FIFO and later, after the process was resumed, the following check for the FIFO_MEOF flag did see EOF. We now first check for the FIFO_MEOF flag and later for the amount of data inside as the FIFO as FIFO_MEOF is set after the FIFO content has been updated and thus a context switch is no longer able to cause a wrong assumption about the content of the FIFO. We now did run 250 million tests without seeing another problem. If you still see this, please send a report. - star: Note that the debug output for this problem now has been disabled. If you need to debug this, call: smake clean COPTX=-DFIFO_EOF_DEBUG all in the star directory. - star: The message "Sync pipe read error" is no longer printed when the FIFO background process dies instead of sending a final wakeup. This is needed since there is a possibility for a context switch in the foreground process that can make it later wait for a wakeup while the background process misses to see the wait flag and just exits. - star: In rare conditions (once every 2 million tries), a hang could. occur with "star -c" if the tar process fills the FIFO and sets the EOF flag and then calls wait() to wait for the FIFO tape output process. This happens in case that the tape output did not see the EOF flag because it has undergone a context switch after it checked for the not yet existing EOF flag and before waiting for a wakeup from the tar FIFO fill process. Star now closes the sync pipes before calling wait() as this always wakes up the waiting other side. We did run another 300 million tests for this condition and did not see any problem now. - star: The version is now 1.6 Short overview for what changed since the last "stable" version: - Support for "infinitely" long path names has been added. - Support for comparing timestamps with nanosecond granularity - -secure-links has been made the default when extracting archived (except when doing an incremental restore). - Added Support for NFSv4 ACLs on FreeBSD. Solaris has been supported since 2013. - Added Support to archive SELinix attributes. - Allow to configure whether "star -fsync" is the default in order to support filesystems that are slow with granted transactions (like ZFS) or platforms that are genrally slow with fsync() (like Linux). - Full UNICODE support has been added for tar headers. - Support for -zstd compression has been added. - Some rare FIFO problems have been fixed. Note that we did recently run more than a billion tests to verify the FIFO after we identified a method to trigger the problem on Linux. Release 2019-03-11: - star: Support for base-256 numbers in timestams and uid/gid has been added. This has been planned in the 1990s already, when star invented the base-256 coding, but it has been forgotten in favor of the POSIX.1-2001 enhanded archive headers. Now it seems that GNU tar. that copied the format from star uses it for timestamps and uid/gid and we need to implement it in order to get archive compatibility. Thanks to Michal Górny (mgorny@@gentoo.org) for detecting the missing feature. - star: The t_rdev field in the old star header now may use base-256 as well. - star: The function stoli() added a new parameter "fieldwidth" that allows to configure when a "unterminated octal number" warning is printed. This is needed since this function is used for 8 byte and for 12 byte fields. - star: star did print archives with illegal 32 byte user/group. names (where the nul terminator is missing) "correctly", when in. list mode but it used only the first 31 bytes when extractig. such archives - star: a new function istarnumber() is used to do better heuristics on what a valid TAR archive is. We have some special handling to work. around the non-compliance of GNU tar in some known cases. If you discover other GNU tar archives that are not detected as TAR archive, please report them to help to make th eheuristics better. The background is to make star better in detecting fool archives. - star: The directory testscripts added new files: testscripts/not_a_tar_file1 and testscripts/not_a_tar_file3 with correct checksums that fool tar implementations that use too few heuristics to identify tar archives. - star: fixed a bug in the FIFO related to extracting multi-volume archives. The bug was introduced with release 2019-02-18 and the effect was that the FIFO complained at the end of the last volume. - star/libschily: Added new error checking codes: "ID"<-->allows to control error behaviour with range errors in uid_t and gid_t values. "TIME"<>allows to control error behaviour with range errors in time_t - star: Creating multi volume archives without using the FIFO did dump core. We thus no longer set mp->chreel = TRUE; when the FIFO has. been disabled. The related bug has been introduced in January 2012. - star: Creating multi volume archives with a very small volume size could cause a hang at the end as the function startvol() did not check whether the TAR process did already decide to exit while waiting for the TAR process to calm down (stop) before writing the next multi volume header. We no longer wait in this case. - star: exprstats() now calls fifo_exit(ret) in order to avoid a FIFO Sync pipe read error message in case that star was terminated with an error. - star: Since we added better Unicode support in May 2018, star did dump core when a multi volume header with POSIX.1-2001 extensions was written in multi volume create mode. We now check for NULL pointers before we call nameascii() to decide whether the file. name needs a UTF-8 translation. - star: Creating multi volume archives without POSIX.1-2001 support no longer sets POSIX.1-2001 extension flags for the volume header. - star: The flag XF_NOTIME now works when creating POSIX.1-2001 extended headers and thus the 'x'-header with time stamps for the volume header tar header is no longer created. This avoids to write atime=1 for the volume number 1 since we encode the volume number in the otherwise useless atime of the volume header when in POSIX.1-1988 TAR mode. - star: the star.1 man page now mentions that the first tar program appeared in 1979 (3 years before star has been started as a project). - star: the star.4 man page now has a "SEE ALSO", a HISTORY and a AUTHOR section. - star: the star.4 man page now has a MULTI VOLUME ARCHIVE HANDLING section. - star: the star.4 man page added a new "BASIC TAR STRUCTURE" section. - star: The ACL reference test archives (formerly available from e.g.: http://sf.net/projects/s-tar/files/alpha/) have been added to the directory star/testscripts/. The files. acl-test.tar.gz acl-test2.tar.gz acl-test3.tar.gz acl-test4.tar.gz acl-test5.tar.gz contain ACLs that use the obsolete method from a POSIX proposal from around 1993 that was withdrawn in 1997 and never has become part of a standard. This method has been implemented in 1993 for UFS on Solaris. GNU tar claims to support this format but really does not support it at all. GNU tar fails to extract the reference tar archives from above and it fails to create a compliant tar archive in create mode. It is strange to see that GNU tar never has been tested against the reference archives that have been created in collaboration with SuSE in 2001 already. The files acl-nfsv4-test.tar.gz acl-nfsv4-test2.tar.gz acl-nfsv4-test3.tar.gz acl-nfsv4-test4.tar.gz acl-nfsv4-test5.tar.gz contain ACLs that have become part of the NFSv4 standard and that. are also used on NTFS and ZFS. This format is completely unsupported by GNU tar. - star TODO: create unit tests in order to avoid future problems with multi volume archives similar to the problems we recently fixed. - star: Updated version 1.6 (not yet published in separate tarball) Short overview for what changed since the last "stable" version: - Support for "infinitely" long path names has been added. - Support for base-256 numbers in timestams and uid/gid has been added. This has been planned in the 1990s already, when star invented the base-256 coding, but it has been forgotten in favor of the POSIX.1-2001 enhanded archive headers. - Support for comparing timestamps with nanosecond granularity - -secure-links has been made the default when extracting archived (except when doing an incremental restore). - Added Support for NFSv4 ACLs on FreeBSD. Solaris has been supported since 2013. - Added Support to archive SELinix attributes. - Allow to configure whether "star -fsync" is the default in order to support filesystems that are slow with granted transactions (like ZFS) or platforms that are genrally slow with fsync() (like Linux). - Full UNICODE support has been added for tar headers. - Support for -zstd compression has been added. - Some rare FIFO problems have been fixed. Note that we did recently run more than a billion tests to verify the FIFO after we identified a method to trigger the problem on Linux. @ text @d3 4 a6 4 SHA1 (schily-2019-03-11.tar.bz2) = e3441506ec8bfaed1e55e09208d7054c728c8f57 RMD160 (schily-2019-03-11.tar.bz2) = 49a4d8dc73ab1c1a66db655470c37d29c77d24f1 SHA512 (schily-2019-03-11.tar.bz2) = 04f289c08b2cd6c1954600796798642ac6228dd61fbb37abeff400cbb3a30eeb481c8b6e51fa77dc506329947a4dd04021fe553516286055d586a31834e4cd98 Size (schily-2019-03-11.tar.bz2) = 4289082 bytes @ 1.14 log @star: update to 1.5.4nb1. Packaged for wip by Michael Bäuerle. Changes: too many to list, last distfile was from 2003. @ text @d3 4 a6 4 SHA1 (schily-2018-10-30.tar.bz2) = 2c70cd99d732c70193577d61793c32399fcc7378 RMD160 (schily-2018-10-30.tar.bz2) = f5a843cde89f3e5d54b1925da288fab97990d3eb SHA512 (schily-2018-10-30.tar.bz2) = 72765d11eff52f744a707605a53365da69037c3d982c7b8f4cee98f109f856ee28af3420f63c3fe5a7890649c4eb0fa4dd69d367b7ec41026f288d6237c98d96 Size (schily-2018-10-30.tar.bz2) = 4311065 bytes @ 1.13 log @Add SHA512 digests for distfiles for archivers category Problems found with existing distfile for eagle: distfiles/bicom101.zip distfiles/szip-2.1nb3/szip-2.1.tar.gz distfiles/xmill-0.9.1.tar.gz No changes made to these distinfo files. Otherwise, existing SHA1 digests verified and found to be the same on the machine holding the existing distfiles (morden). All existing SHA1 digests retained for now as an audit trail. @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.12 2012/01/30 03:43:58 sbd Exp $ d3 4 a6 13 SHA1 (star-1.4.3.tar.gz) = c59b68d97edba77a9ac6000be04d457ded1eefe9 RMD160 (star-1.4.3.tar.gz) = f7ec71bfab1723c994e5eed7e6818394a41d44d9 SHA512 (star-1.4.3.tar.gz) = 984001fe5c32775706d1e36220e1bccd2ffc4d87a969df05b5953b55192b2dc7ac663449c09688b87c13d6e57e1a230f79dc0aedecfe9e0f7e9ddbbb70f6ee0d Size (star-1.4.3.tar.gz) = 520388 bytes SHA1 (patch-aa) = 4fe4af396adf23eb7ac071b02a7bf726ab1e4318 SHA1 (patch-ab) = aea3af88d3bedf2ce7a7744c90062ba4e57bb79f SHA1 (patch-ac) = 81e6361db3903e5b04fae4e70ad3a37f9a2f4fa7 SHA1 (patch-ad) = 2be98feac17350b37c242a6f84f539e81330ee14 SHA1 (patch-ae) = 9f08ee4a8f1f150d08d8c4688e0c5061ad2db52e SHA1 (patch-af) = b28ca20dd8cd5326a9d9836880f09740abca7525 SHA1 (patch-lib_fexec.c) = 5a40df04d84c0e44037cdcc723325cce741e2e0f SHA1 (patch-star_fflags.c) = 66fb755de21734eed5c18c896c7aa2ed13696d99 SHA1 (patch-star_star__unix.c) = 3c478f3cd166f8ee03477a3cb00ef8609be53f4b @ 1.12 log @Rename custom function "fexecve", which conflicts with glibc's fexecve(3), to schily_fexecve. Also must be included before . @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.11 2011/01/15 17:46:01 tron Exp $ d5 1 @ 1.11 log @Fix build under NetBSD-currenty removing unused custom function "getline" which conflicts with getline(3). @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.10 2010/09/28 17:50:07 tnn Exp $ d10 1 a10 1 SHA1 (patch-ae) = 34786fc3c51ef14ca2ae9250d8d12d12788abdc5 d12 3 @ 1.10 log @fix local patch; void function cannot return vaule. reported by in #pkgsrc @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.9 2008/06/08 02:40:38 tonnerre Exp $ d10 2 @ 1.10.4.1 log @Pullup ticket 3326 - requested by tron build fix Revisions pulled up: - pkgsrc/archivers/star/distinfo 1.11 Files added: pkgsrc/archivers/star/patches/patch-ae pkgsrc/archivers/star/patches/patch-af ------------------------------------------------------------------------- Module Name: pkgsrc Committed By: tron Date: Sat Jan 15 17:46:02 UTC 2011 Modified Files: pkgsrc/archivers/star: distinfo Added Files: pkgsrc/archivers/star/patches: patch-ae patch-af Log Message: Fix build under NetBSD-currenty removing unused custom function "getline" which conflicts with getline(3). To generate a diff of this commit: cvs rdiff -u -r1.10 -r1.11 pkgsrc/archivers/star/distinfo cvs rdiff -u -r0 -r1.1 pkgsrc/archivers/star/patches/patch-ae \ pkgsrc/archivers/star/patches/patch-af @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.11 2011/01/15 17:46:01 tron Exp $ a9 2 SHA1 (patch-ae) = 34786fc3c51ef14ca2ae9250d8d12d12788abdc5 SHA1 (patch-af) = b28ca20dd8cd5326a9d9836880f09740abca7525 @ 1.9 log @Fix directory traversal vulnerability (CVE-2007-4134) in star. @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.8 2007/12/30 17:25:42 cjep Exp $ d9 1 a9 1 SHA1 (patch-ad) = 8e9fff0b8345a1997ae08a5c5e57260b4c5f8090 @ 1.8 log @Star treats BSD and SysV differently for man page installation. Since we "own" the filesystem underneath LOCALBASE (e.g. /usr/pkg), let's stick with BSD-style installation for this package. This addresses PR#29725. @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.7 2005/02/23 14:45:26 agc Exp $ d9 1 @ 1.8.4.1 log @Pullup ticket #2420 - requested by tonnerre Security patch for star Revisions pulled up: - archivers/star/Makefile 1.22 - archivers/star/distinfo 1.9 - archivers/star/patches/patch-ad 1.1 --- Module Name: pkgsrc Committed By: tonnerre Date: Sun Jun 8 02:40:38 UTC 2008 Modified Files: pkgsrc/archivers/star: Makefile distinfo Added Files: pkgsrc/archivers/star/patches: patch-ad Log Message: Fix directory traversal vulnerability (CVE-2007-4134) in star. @ text @d1 1 a1 1 $NetBSD$ a8 1 SHA1 (patch-ad) = 8e9fff0b8345a1997ae08a5c5e57260b4c5f8090 @ 1.7 log @Add RMD160 digests in addition to SHA1 ones. @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.6 2004/05/02 22:26:12 danw Exp $ d8 1 @ 1.6 log @fix install user/group on darwin @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.5 2003/02/23 11:28:59 salo Exp $ d4 1 @ 1.5 log @Updated to version 1.4.3. Changes: - Support for BSDi version 4.x - Suport for BSDi on sparc - Support for sparc64 FreeBSD - Support for i786-cygwin - Added +DAportable to the HP-UX cc compiler flags - New Platform 9000-831-hp-ux-cc - Added floatingpint printing support for OS/2 - Added support for macppc-netbsd-cc NetBSD on MAC - Workaround for an OpenBSD bug in ctype.h (illegaly #defines EOF) - Added IPv6 support to 'rmt' - Better casting for debug printf() in 'rmt' - Better autoconfiguration for librmt and its users yields in better compilation and portability results for OS that do not support the needed internet features for remote tape support. - Special support for an undocumented but unfortunately important "feature" for symlinks on HP-UX. Now star tries to retain the permissions of a symlink by stting umask() before creating the symlink. - Fixed a bug that caused star to be unable to correctly deal with ACLs where the user or group name contains spaces. - Workaround for reading rotten archives caused by above bug. - Fixed a bug that caused star to create broken archives if the POSIX.1-2001 extended format is used for sparse files > 8 GB. For this reason, a new extended header tag SCHILY.realsize has been added. - Fixed a bug that caused star to dump core on UNIX-98 TAR compat mode with e.g. 'star cbv' because star did not check for the missing arg to the -b option. - 'star -n -tpath ...' now only prints the pathnames to allow to use the ooutput directly in scripts. If you like the old behavior, use 'star -nv ...' @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.4 2002/12/16 23:21:06 grant Exp $ d6 1 @ 1.4 log @Updated star to 1.4.2. Major changes since 1.4.1: - printf() now correctly handles %X vs. %x on 64 bit machines Removed a 20 year old local extension that became non-portable. - new 'librmt', which may be used by any external program like e.g. dump/restore to improve cross platform compatibility. - librmt now allows the use of ssh(1) for remote tape access. - smt benefits from librmt and now gives platform independent 'mt status' output in remote mode. - New option -wready for smt. - Better man page for 'rmt'. - Handle a seek error problem in create mode correctly when checking for reading past max possible file size on non-large file OS. - Correctly propagate write/read errors from FIFO to star. - Add support for SIGINFO (*BSD) as a courtesy to BSD users. - Do not open /dev/tty if a newvolume script is present. This allows the use of star from cron scripts. - Fixed a bug in the ACL handling code on Linux that caused star to recognize ACL comments as ACL entries and include them in the archive. - Work around to allow star to read ACL enhanced archives that include bogus entries that really were ACL comments created by the bug above. The full list of changes can be found at: ftp://ftp.fokus.gmd.de/pub/unix/star/AN-1.4.2 @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.3 2002/09/25 06:35:48 cjep Exp $ d3 2 a4 2 SHA1 (star-1.4.2.tar.gz) = 93c19b4ce38fcbd8a0412c8fdba5c9dabec0c6cb Size (star-1.4.2.tar.gz) = 515619 bytes @ 1.3 log @Make this package build on arm. The same principle should apply to other CPU families, but I haven't tested those. @ text @d1 1 a1 1 $NetBSD: distinfo,v 1.2 2002/07/02 12:40:13 wiz Exp $ d3 2 a4 2 SHA1 (star-1.4.1.tar.gz) = 8f8b0ee1c7c83040de9607db0ae63da221957f69 Size (star-1.4.1.tar.gz) = 496283 bytes @ 1.2 log @Add RCS Id. @ text @d1 1 a1 1 $NetBSD$ d5 1 @ 1.2.4.1 log @file distinfo was added on branch buildlink2 on 2002-08-21 22:42:03 +0000 @ text @d1 4 @ 1.2.4.2 log @Merge from pkgsrc-current in pkgsrc/archivers. @ text @a0 4 $NetBSD: distinfo,v 1.2.4.1 2002/08/21 22:42:03 jlam Exp $ SHA1 (star-1.4.1.tar.gz) = 8f8b0ee1c7c83040de9607db0ae63da221957f69 Size (star-1.4.1.tar.gz) = 496283 bytes @ 1.1 log @Initial revision @ text @d1 1 a1 1 @ 1.1.1.1 log @Initial import of Star 1.4.1. DESCR is written by the author, Joerg Schilling . Star is a full-featured tar command that can access local and remote tar archives (files and tapes). It reads and writes POSIX compliant tar archives as well as non-POSIX GNU tar archives. Star is the first POSIX.1-2001 compliant tar implementation. It includes a FIFO for speed, a pattern matcher, multi-volume support, the ability to archive sparse files and ACLs and the ability to archive extended file flags. It supports utomatic archive format detection, automatic byte order recognition, automatic archivecompression/decompression. It includes the only known platform independent "rmt" server program that implements all Sun/GNU/Schily/BSD enhancements and allows any "rmt" client from any OS to contact any OS as server. @ text @@