[no description] https://git.osdyson.ru/mirror/pkgsrc/atom?h=pkgsrc_2011Q1 2010-02-19T18:55:56Z 2010-02-19T18:55:56Z joerg joerg 2010-02-19T18:55:56Z urn:sha1:76ad1cc0afa70ade602a9fcf3558823603694811 2009-12-14T23:33:01Z heinz heinz 2009-12-14T23:33:01Z urn:sha1:cf36f5343cb8db4e8462a7e51fd1bee8b078f189 2008-07-29T17:21:39Z pgoyette pgoyette 2008-07-29T17:21:39Z urn:sha1:402915f314b7651157bd9715ad76bddda49f7e47 configured for IPv4 only. IPv6 can still be enabled via PKG_OPTIONS. Fixes my PR pkg/38957 ok gdt@ 2008-02-15T16:23:09Z gdt gdt 2008-02-15T16:23:09Z urn:sha1:2fbec389c11dacbe619c0fcf550b98e851cbce5a [bugfixes and minor improvements omitted; see NEWS] Changes in release 2.5.2 * krb5 auth is working * Works with IPv6 address * Amanda configuration file changes o amanda.conf changes + debugging is enabled in the config file see all debug_* config option + tapetype 'readblocksize', if maxtapeblocksize is set too larger for your hardware * Amanda command changes o amadmin: new 'holding list' and 'holding delete' subcommand. Changes in release 2.5.1p3 * Works with tar-1.16 and exit status of 1. Changes in release 2.5.1p2 * amoverview is working * dumptype starttime is working * Amanda command changes o amtape accept the -o arguments o amgetconf --list to list all tapetype, dumptype, holdingdisk or interface o amgetconf can return a value of a specific tapetype, dumptype, holdingdisk or interface Changes in release 2.5.1p1 * Remove contrib/sst. Changes in release 2.5.1 * Defects found by Coverity scan and Klocwork K7 analysis tools fixed. * Works with GNU tar 1.15.91 - work with new gtar state file format. * Open SSL encryption support * Two new authentication methods: bsdtcp, bsdudp. * Unlimited number of DLEs on a client with bsdtcp, rsh and ssh authentication methods. * Recovery process amrecover uses Secure API. amoldrecover command (same syntax and functionality as amrecover command) is provided for compatibility with old Amanda releases. amoldrecover command uses old amidxtaped/amindexd protocol. * Amanda debug files are separated into client/server/amandad and are also classified based on Amanda configuration name. * Amanda command changes o amfetchdump -o is replaced by -O. o amcheck -w option does all tests including the tape writable test. Use amcheck -t -w to do only the tape writable test. o -o command option to override Amanda configuration. See amanda man page for details. o amgetconf command doesn't write the BUGGY message when a entry is not found in the configuration file. * Amanda configuration file changes o amanda.conf changes + amrecover_do_fsf in amanda.conf defaults to yes + amrecover_check_label in amanda.conf defaults to yes + usetimestamps in amanda.conf to support multiple backup runs in a calendar day. + holdingdisk in amanda.conf supports new values: NEVER, AUTO, REQUIRED. + amandad_path, client_username and ssh_keys in amanda.conf for ssh/rsh authentication. o New amanda client configuration file - amanda-client.conf. Different client configuration file can be used for each Amanda configuration. + gnutar_list-dir and amandates can be specified in Amanda client configuration file - amanda-client.conf o .amandahosts format changes to allow use of secure API for recovery. o Amanda service entries in xinetd configuration has changed. Changes in release 2.5.0p1 * Add the 'amtape update' command. Changes in release 2.5.0 * Communication security/authentication: Kerberos 4/5, OpenSSH * Data security: Symmetric/Assymetric encrytion algorithms (aesutil and gpg encryption), Encryption can be done on server or client, Custom encryption utilities can be used. * Compression: Ability to add custom compression tools. This is a really useful feature especially since it can specified for a DLE. You can use different compression algorithm for images, binaries, ascii files and so on. * Dump images spanning multiple media volumes - Dump images are no longer restricted to a single media volume (tape or vtape). Data restoration can be done using amrecover and amfetchdump commands. * Auto tape labelling - This optional feature is good for disk backups. Change in release 2.4.5 * new displayunit global option to select the unit use to display number k=kilo, m=mega, g=giga, t=tera. * new amoverview -skipmissed option. Change in release 2.4.5b1 * holding disk disk use timestamped directory. * autoflush flush today's dump. * new bumppercent global option, this should improve bumping criteria, the bumpsize is set to a fixed value which can be adequate for small and large disk. * bumpsize, bumppercent, bumpdays and bumpmult can be in a dumptype. * calcsize support include and exclude like gnutar. * new 'estimate' dumptype option to select estimate type: CLIENT: estimate by the dumping program. CALCSIZE: estimate by the calcsize program, a lot faster but less acurate. SERVER: estimate based on statistic from previous run, take second but can be wrong on the estimate size. 2007-07-04T20:54:31Z jlam jlam 2007-07-04T20:54:31Z urn:sha1:45233ac07a4c6f9e80f4f9350cbb54ee23d8bd54 the owner of all installed files is a non-root user. This change affects most packages that require special users or groups by making them use the specified unprivileged user and group instead. (1) Add two new variables PKG_GROUPS_VARS and PKG_USERS_VARS to unprivileged.mk. These two variables are lists of other bmake variables that define package-specific users and groups. Packages that have user-settable variables for users and groups, e.g. apache and APACHE_{USER,GROUP}, courier-mta and COURIER_{USER,GROUP}, etc., should list these variables in PKG_USERS_VARS and PKG_GROUPS_VARS so that unprivileged.mk can know to set them to ${UNPRIVILEGED_USER} and ${UNPRIVILEGED_GROUP}. (2) Modify packages to use PKG_GROUPS_VARS and PKG_USERS_VARS. 2007-01-05T12:47:27Z obache obache 2007-01-05T12:47:27Z urn:sha1:69a59d0379a201d67a6d871bfa657972a84f9e8c 2006-10-02T21:05:44Z rillig rillig 2006-10-02T21:05:44Z urn:sha1:4ce862babf65744e3e2d00cd3ead4d434d94104f 2006-07-19T19:14:37Z jlam jlam 2006-07-19T19:14:37Z urn:sha1:69621913228b1ea1d22363e660624daf85b3602c had actually been ignoring LTCONFIG_OVERRIDE anyway and just using the default LIBTOOL_OVERRIDE to replace libtool scripts in packages. This just formalizes the fact that LTCONFIG_OVERRIDE is not used meaningfully by pkgsrc. 2006-05-26T13:19:38Z joerg joerg 2006-05-26T13:19:38Z urn:sha1:30e79be084190b2c50261cca9a7e74161bb2ce4d and the tools framework already does the right thing. Bump revisions. 2006-03-04T21:28:51Z jlam jlam 2006-03-04T21:28:51Z urn:sha1:48ff096d36ac47701672a4f682e7c4ebafea1eb9 developer is officially maintaining the package. The rationale for changing this from "tech-pkg" to "pkgsrc-users" is that it implies that any user can try to maintain the package (by submitting patches to the mailing list). Since the folks most likely to care about the package are the folks that want to use it or are already using it, this would leverage the energy of users who aren't developers.