head 1.9; access; symbols pkgsrc-2017Q1:1.8.0.22 pkgsrc-2017Q1-base:1.8 pkgsrc-2016Q4:1.8.0.20 pkgsrc-2016Q4-base:1.8 pkgsrc-2016Q3:1.8.0.18 pkgsrc-2016Q3-base:1.8 pkgsrc-2016Q2:1.8.0.16 pkgsrc-2016Q2-base:1.8 pkgsrc-2016Q1:1.8.0.14 pkgsrc-2016Q1-base:1.8 pkgsrc-2015Q4:1.8.0.12 pkgsrc-2015Q4-base:1.8 pkgsrc-2015Q3:1.8.0.10 pkgsrc-2015Q3-base:1.8 pkgsrc-2015Q2:1.8.0.8 pkgsrc-2015Q2-base:1.8 pkgsrc-2015Q1:1.8.0.6 pkgsrc-2015Q1-base:1.8 pkgsrc-2014Q4:1.8.0.4 pkgsrc-2014Q4-base:1.8 pkgsrc-2014Q3:1.8.0.2 pkgsrc-2014Q3-base:1.8 pkgsrc-2014Q2:1.7.0.38 pkgsrc-2014Q2-base:1.7 pkgsrc-2014Q1:1.7.0.36 pkgsrc-2014Q1-base:1.7 pkgsrc-2013Q4:1.7.0.34 pkgsrc-2013Q4-base:1.7 pkgsrc-2013Q3:1.7.0.32 pkgsrc-2013Q3-base:1.7 pkgsrc-2013Q2:1.7.0.30 pkgsrc-2013Q2-base:1.7 pkgsrc-2013Q1:1.7.0.28 pkgsrc-2013Q1-base:1.7 pkgsrc-2012Q4:1.7.0.26 pkgsrc-2012Q4-base:1.7 pkgsrc-2012Q3:1.7.0.24 pkgsrc-2012Q3-base:1.7 pkgsrc-2012Q2:1.7.0.22 pkgsrc-2012Q2-base:1.7 pkgsrc-2012Q1:1.7.0.20 pkgsrc-2012Q1-base:1.7 pkgsrc-2011Q4:1.7.0.18 pkgsrc-2011Q4-base:1.7 pkgsrc-2011Q3:1.7.0.16 pkgsrc-2011Q3-base:1.7 pkgsrc-2011Q2:1.7.0.14 pkgsrc-2011Q2-base:1.7 pkgsrc-2011Q1:1.7.0.12 pkgsrc-2011Q1-base:1.7 pkgsrc-2010Q4:1.7.0.10 pkgsrc-2010Q4-base:1.7 pkgsrc-2010Q3:1.7.0.8 pkgsrc-2010Q3-base:1.7 pkgsrc-2010Q2:1.7.0.6 pkgsrc-2010Q2-base:1.7 pkgsrc-2010Q1:1.7.0.4 pkgsrc-2010Q1-base:1.7 pkgsrc-2009Q4:1.7.0.2 pkgsrc-2009Q4-base:1.7 pkgsrc-2009Q3:1.6.0.2 pkgsrc-2009Q3-base:1.6 pkgsrc-2009Q2:1.5.0.44 pkgsrc-2009Q2-base:1.5 pkgsrc-2009Q1:1.5.0.42 pkgsrc-2009Q1-base:1.5 pkgsrc-2008Q4:1.5.0.40 pkgsrc-2008Q4-base:1.5 pkgsrc-2008Q3:1.5.0.38 pkgsrc-2008Q3-base:1.5 cube-native-xorg:1.5.0.36 cube-native-xorg-base:1.5 pkgsrc-2008Q2:1.5.0.34 pkgsrc-2008Q2-base:1.5 cwrapper:1.5.0.32 pkgsrc-2008Q1:1.5.0.30 pkgsrc-2008Q1-base:1.5 pkgsrc-2007Q4:1.5.0.28 pkgsrc-2007Q4-base:1.5 pkgsrc-2007Q3:1.5.0.26 pkgsrc-2007Q3-base:1.5 pkgsrc-2007Q2:1.5.0.24 pkgsrc-2007Q2-base:1.5 pkgsrc-2007Q1:1.5.0.22 pkgsrc-2007Q1-base:1.5 pkgsrc-2006Q4:1.5.0.20 pkgsrc-2006Q4-base:1.5 pkgsrc-2006Q3:1.5.0.18 pkgsrc-2006Q3-base:1.5 pkgsrc-2006Q2:1.5.0.16 pkgsrc-2006Q2-base:1.5 pkgsrc-2006Q1:1.5.0.14 pkgsrc-2006Q1-base:1.5 pkgsrc-2005Q4:1.5.0.12 pkgsrc-2005Q4-base:1.5 pkgsrc-2005Q3:1.5.0.10 pkgsrc-2005Q3-base:1.5 pkgsrc-2005Q2:1.5.0.8 pkgsrc-2005Q2-base:1.5 pkgsrc-2005Q1:1.5.0.6 pkgsrc-2005Q1-base:1.5 pkgsrc-2004Q4:1.5.0.4 pkgsrc-2004Q4-base:1.5 pkgsrc-2004Q3:1.5.0.2 pkgsrc-2004Q3-base:1.5 pkgsrc-2004Q2:1.4.0.2 pkgsrc-2004Q2-base:1.4 pkgsrc-2004Q1:1.3.0.4 pkgsrc-2004Q1-base:1.3 pkgsrc-2003Q4:1.3.0.2 pkgsrc-2003Q4-base:1.3 buildlink2-base:1.2 netbsd-1-5-RELEASE:1.1 netbsd-1-4-PATCH003:1.1; locks; strict; comment @# @; 1.9 date 2017.05.20.06.53.05; author spz; state dead; branches; next 1.8; commitid JSogv69a3lQrY5Sz; 1.8 date 2014.08.03.17.33.34; author spz; state Exp; branches; next 1.7; commitid ZeipQVABT84TlWKx; 1.7 date 2009.12.16.22.10.25; author spz; state Exp; branches; next 1.6; 1.6 date 2009.09.22.13.17.00; author spz; state Exp; branches; next 1.5; 1.5 date 2004.07.24.23.55.28; author grant; state Exp; branches; next 1.4; 1.4 date 2004.06.02.11.43.55; author tron; state Exp; branches; next 1.3; 1.3 date 2003.07.29.16.27.27; author wiz; state Exp; branches; next 1.2; 1.2 date 2001.02.08.16.23.07; author tron; state dead; branches; next 1.1; 1.1 date 2000.08.17.14.00.28; author wiz; state Exp; branches; next ; desc @@ 1.9 log @update to 2.6.1. Excerpt from NEWS: Upgrading from 2.5 to 2.6 The following changes require your full attention because a manual intervention may be needed: The name and location of the pullnews configuration file have changed. It is now pullnews.marks, located in pathdb when pullnews is run as the news user, or otherwise in the running user's home directory. This file was previously stored in .pullnews in the running user's home directory (even for the news user). If you use pullnews, you need to manually move and rename the configuration file; otherwise, it will no longer work. Note that the -c flag passed to pullnews allows to specify another configuration file, if need be. The default location of the mailpost database directory has changed from pathtmp to pathdb. If you use mailpost without an explicitly specified database directory (using the -b flag), then you should manually move your current database files mailpost-msgid.dir and mailpost-msgid.pag from pathtmp to pathdb. If you have been using TLS/SSL with nnrpd before, be aware that the default value of a few inn.conf parameters have changed: the server now decides the preferred cipher (instead of the client), and only TLS protocols are allowed (using the flawed SSLv2 and SSLv3 protocols is now disabled). If you want to change these settings, the respective tlspreferserverciphers and tlsprotocols parameters can be tuned to your needs. The --with-kerberos configure flag used to add Kerberos v5 support has been renamed to --with-krb5. The --with-berkeleydb configure flag used to add Berkeley DB support has been renamed to --with-bdb. The --enable-ipv6 configure flag no longer exists. IPv6 is now unconditionally enabled, if available. $HOME is no longer exported as an environment variable by innshellvars, innshellvars.tcl and the Perl module INN::Config. It was previously overriding the default user home directory with pathnews. If you use these scripts in your own scripts, you will have to take care of that change. Owing to the implementation of RFC 4643 (AUTHINFO USER/PASS) in innd, if remote peers have to authenticate in order to feed articles, they now have to send a username (which was previously wrongly optional), before sending their password. The mandatory username, though currently unused by innd, can be whatever the remote peer wishes. In previous versions of INN, inncheck was already complaining when passwd.nntp contained an empty username associated with a password. A manual review of authenticated feeds should then be done so as to ensure that they are properly working. The Injection-Date: and Injection-Info: headers are now generated by nnrpd at injection time instead of the NNTP-Posting-Date:, NNTP-Posting-Host:, X-Complaints-To: and X-Trace: headers. Local scripts that were using (for authentication, privacy, etc.) these now deprecated headers should be updated. Also note that the Path: header of locally posted articles can also contain the contents of the deprecated NNTP-Posting-Host: field. The two addnntppostingdate and addnntppostinghost parameters in inn.conf have been respectively renamed to addinjectiondate and addinjectionpostinghost. innupgrade takes care of the modification only for inn.conf; a manual change will therefore be needed for readers.conf, if these parameters are overridden in this file. The default values of a few inn.conf parameters have changed to make use of the vastly expanded storage and RAM commonly available today: datamovethreshold (from 8192 to 16384), msgidcachesize (from 16000 to 64000), overcachesize (from 64 to 128), and wireformat (now enabled by default). The generation of status reports and performance timings are now also enabled by default: logstatus and nnrpdoverstats parameters, with a frequency of 10 minutes (status and timer parameters). The default value of max-queue-size has changed from 5 to 20, and use-mmap now defaults to true for innfeed.conf. Changes in 2.6.1 nnrpd now uses -0000 as the time zone for Date: and Injection-Date: header fields it generates. It was previously using +0000, wrongly systematically indicating a local time zone at Universal Time when localtime is set to false (which is the default) in readers.conf. The +0000 time zone will now be used only if localtime is set to true and UTC is really the local time zone of the server. Julien Elie has implemented in nnrpd the new COMPRESS command described in draft-murchison-nntp-compress that extends the NNTP protocol to allow a connection to be effectively and efficiently compressed. News clients that also support that extension will be able to benefit from that bandwidth optimization and improvement in speed. Moreover, using COMPRESS is more secure than TLS-level compression, as far as authentication credentials are concerned. The default value for the tlscompression parameter in inn.conf has changed. TLS-level compression is now disabled by default, to comply with the best current practices for a secure use of TLS in application protocols like NNTP. Using the new COMPRESS command is recommended. The tlscompression parameter in inn.conf now also permits to disable TLS-level compression with OpenSSL 0.9.8. It previously had an effect only when OpenSSL 1.0.0 or later was used. rnews no longer segfaults at startup when started setuid news. Thanks to Marcus Jodorf for the bug report. Fixed slow nnrpd responses for a few NNTP commands. The TCP_NODELAY option was unconditionally set whereas only BSD/OS systems needed it. Thanks to Christian Mock for having discovered that. Articles containing a Received: or a Posted: header field are no longer rejected by nnrpd at injection time. Articles containing control characters or whitespace-only content lines in their headers are now rejected by nnrpd at injection time. OpenSSL 1.1.0 support has been added to INN. When an encryption layer is negotiated during a successful use of the STARTTLS command, or after a successful authentication using a SASL mechanism that negotiates an encryption layer, nnrpd now updates the permissions of the news client according to the new secure state of his connection (that is to say auth blocks in readers.conf using the require_ssl parameter are taken into account). Previously, only connections on a dedicated port (usually 563) were taking benefit from that parameter. Thanks to Steve Crook for the bug report. When a data integrity layer was negotiated during a successful SASL authentication, nnrpd was wrongly reseting any knowledge obtained from the client, such as the current newsgroup and article number. This behaviour now applies only when an encryption layer is negotiated. nntpsend now correctly waits until all of the child innxmit processes exit before it does. It was causing nntpsend to fail to work properly on systems that use systemd, because when it exits prematurely, systemd kills all of the processes it launched, including the innxmit processes. Thanks to Jonathan Kamens for the patch. Update from GNU Libtool 2.4.2 to 2.4.6. Other minor bug fixes and documentation improvements. Changes in 2.6.0 The NNTP protocol requires a username to be sent before a password when authentication is used. innd was wrongly allowing only a password to be sent by authenticated peers. See the note above for more details. The Lines: header is no longer generated by nnrpd at injection time. The Injection-Date: header is now generated by nnrpd at injection time instead of the deprecated NNTP-Posting-Date: header, when addinjectiondate is set to true. Note that addnntppostingdate has been renamed to addinjectiondate in inn.conf. The Injection-Info: header is now generated by nnrpd at injection time instead of the deprecated NNTP-Posting-Host: (when addinjectionpostinghost is set to true), X-Complaints-To: and X-Trace: headers. Note that addnntppostinghost has been renamed to addinjectionpostinghost in inn.conf. The Path: header of locally posted articles now also contains the contents of the NNTP-Posting-Host: header. A new addinjectionpostingaccount parameter has been added in inn.conf. When set to true, the Injection-Info: header field contains an additional posting-account attribute that mentions the username assigned to the user at connection time or after authentication. The default value for this parameter is false. A few headers are now considered as obsolete by nnrpd at injection time: NNTP-Posting-Date:, NNTP-Posting-Host:, X-Complaints-To:, X-Trace:, Also-Control:, Article-Names:, Article-Updates:, and See-Also: headers. Besides, nnrpd will similarly reject obsolete sendsys, senduuname and version control messages. The presence of a Subject: header field beginning with cmsg no longer causes an article to be interpreted as a control message by nnrpd at injection time. nnrpd no longer differentiates IHAVE from POST. Articles injected with IHAVE are now treated as though they were injected with POST. It means that if the previous behaviour of IHAVE was expected, innd should handle itself the connection instead of nnrpd. The name of the pullnews configuration file is now pullnews.marks located in pathdb when pullnews is run as the news user, or otherwise in the running user's home directory. It was previously stored in .pullnews in the running user's home directory (even for the news user). Fixed a leak of semaphores when using buffindexed. Thanks to Richard Kettlewell for having fixed the issue. Building with Libtool is no longer optional. The --enable-libtool option to configure has been removed. DESTDIR and non-root installs are now properly supported and documented in INSTALL. The make install, make update and make cert steps properly obey DESTDIR. Besides, it is no longer a requirement that the installation step be done by the superuser, as long as the user executing the install has supplied a DESTDIR value that points to a writable directory, and the person or process performing the install corrects the file ownerships when INN is installed on the system on which it's going to run. Thanks to James Ralston for this support. When building INN with Berkeley DB, Cyrus SASL, Kerberos v5, OpenSSL, or zlib support, no longer add standard locations to compiler and linker include flags. Such default paths are now added only if explicitly given to one or more of the --with-bdb, --with-bdb-include, --with-bdb-lib, --with-sasl, --with-sasl-include, --with-sasl-lib, --with-krb5, --with-krb5-include, --with-krb5-lib, --with-openssl, --with-openssl-include, --with-openssl-lib, --with-zlib, --with-zlib-include, or --with-zlib-lib configure flags (the flags ending with -include and -lib are new in INN 2.6.0). If the Berkeley DB, Cyrus SASL, Kerberos v5, or OpenSSL SSL and crypto libraries are found at configure time, INN will now be built with support for them unless respectively the --without-bdb, --without-sasl, --without-krb5, or --without-openssl flags are explicitly passed to configure. Note that it was already the default behaviour for zlib support when Berkeley DB support was also enabled. The configure flag --enable-reduced-depends has been added to request that library probes assume shared libraries are in use and dependencies of libraries should not be probed. It therefore tries to minimize the shared library dependencies of the resulting binaries on platforms with proper shared library dependencies. This is not enabled by default, and is of interest primarily to people building packages for distributions. Building INN with Python support now requires the use of Python 2.2.0 or later as the distutils.sysconfig module used was introduced with Python 2.2.0. The INN test suite driver is now fully synchronized with the upstream version of the C TAP Harness package maintained by Russ Allbery. Keeping the INN test suite driver up-to-date will be possible thanks to a new getc-tap-harness script in the support directory that automatically fetches the latest upstream changes. Similarly, the new getrra-c-util script permits to keep most of the utility and portability functions synchronized with the upstream version of the rra-c-util package maintained by Russ Allbery. Other minor bug fixes and documentation improvements. @ text @$NetBSD: patch-ai,v 1.8 2014/08/03 17:33:34 spz Exp $ --- include/inn/dbz.h.orig 2014-05-17 08:24:49.000000000 +0000 +++ include/inn/dbz.h @@@@ -38,7 +38,7 @@@@ typedef struct { bool nonblock; } dbzoptions; -#ifdef __GNUC__ +#if defined(__GNUC__) && !defined(PACKED) #define PACKED __attribute__ ((packed)) #else #if !defined(PACKED) @ 1.8 log @update INN to version 2.5.4. Excerpt from the upstream release announcement: Changes in 2.5.4 * An up-to-date control.ctl file is provided with this release. You should manually update your control.ctl file with the new information recorded about Usenet hierarchies. * A test has been improved in innwatch.ctl so that innwatch no longer throttles innd when no overview directory exists. You should manually update your innwatch.ctl file to get this improvement. * Fixed a long-standing limitation on how controlchan and pgpverify were checking the signer of control messages. They now properly handle the case of several UIDs being defined on a single PGP key, as well as the presence of spaces into UIDs. In previous versions of INN, a few valid control messages got ignored because of that limitation (fido.ger.* and grisbi.* were for instance impacted). * As the name of the radius.conf configuration file shipped with INN for the nnrpd authenticator against a RADIUS server conflicts with the libradius package, this file is renamed to inn-radius.conf (innupgrade takes care of the rename during the update). * The attributes hash is now accessible to nnrpd Perl posting filter. As a result, filter_nnrpd.pl can make use of it. Only authentication and access Perl hooks could previously use the attributes hash. Thanks to Steve Crook for this addition. * INN now properly builds fine with flex 2.5.36 (this version introduced a change of type for a variable used by INN). * When using funnel feeds, innfeed log files were open forever, which resulted in empty log files, once rotated by scanlogs. innfeed now reopens its log files upon receiving a HUP signal; this signal is in particular sent by scanlogs during log rotation. Thanks to Florian Schlichting for the patch. * Exploder and process channels are now reopened when "ctlinnd flushlogs" is used. Otherwise, they could hold open an already deleted errlog file. The issue affected in particular controlchan or ninpaths, running as such channels. * Fixed a buffer overflow when using imapfeed with more than a million commands during the same IMAP session. Thanks to David Binderman for the bug report. * Fixed a segfault occurring in innd on systems where time_t is a 64-bit integer. Thanks to S.P. Zeidler for the patch. * Fixed a segfault occurring in nnrpd when a res block was used in readers.conf without the program: key. * Fixed an issue where users were denied posting because of an overlapping buffer copy in a check nnrpd was doing. Thanks to Florian Schlichting for the patch. * Fixed a regression that occurred in INN 2.5.3 regarding the path used by default by pullnews for its configuration file. Instead of looking in the running user's home directory, it was looking in the *pathnews* directory set in inn.conf. Thanks to Tony Evans for the bug report. * When neither wget nor ncftpget nor ncftp was found at configure time, the path to the simpleftp substitution program shipped with INN was not properly set in innshellvars, innshellvars.pl, and the "INN::Config" Perl module. Thanks to Christian Garbs for the bug report. * ckpasswd no longer tries to use the ndbm compatibility layer provided by Berkeley DB if Berkeley DB has been built without ndbm support. Also add support for gdbm libraries in ckpasswd. * Fixed a Perl warning in inncheck; using "defined(@@array)" has been deprecated since Perl 5.16. * Fixed the occurrence of an unexpected "cant select" error generated by innd. Thanks to Paul Tomblin for having caught that long-standing issue. * When building INN with Berkeley DB support, no longer add -L/usr/lib to the linker include flags; unconditionally adding it may break the build on systems using lib32 and lib64 directories. * On a fresh INN install, motd.innd and motd.nnrpd are no longer installed by default. Instead, samples for these files are provided in *pathetc*, named differently so that their default contents are not displayed to news clients before they get customised. * Other minor bug fixes and documentation improvements (like the addition in the readers.conf man page of the log: and program: parameters in res blocks, and the include directive). @ text @d1 1 a1 1 $NetBSD: patch-ai,v 1.7 2009/12/16 22:10:25 spz Exp $ @ 1.7 log @The next minor version of INN. From the release announcement: Major changes from 2.5.0 to 2.5.1 * Fixed a segfault in imap_connection which could occur when SASL was used. * Fixed a segfault in the keyword generation code which was assuming that an article was nul-terminated. Fixed another segfault in the keyword generation code when an article already contained a Keywords: header. Thanks to Nix for the bug reports. * Owing to the US-CERT vulnerability note VU#238019, Cyrus SASL library has slightly changed. imap_connection and nnrpd now handle that change. Otherwise, some answers are too long to be properly computed during SASL exchanges. * Fixed a memory allocation problem which caused nnrpd to die when retrieving via HDR/XHDR/XPAT the contents of an extra overview field absent from the headers of an article. The NEWNEWS command was also affected on very rare cases. Thanks to Tim Woodall for the bug report. * HDR/XHDR/XPAT answers are now robust when the overview database is inconsistent. When the overview schema was modified without the overview database being rebuilt, wrong results could be returned for extra fields (especially a random portion of some other header). The desired header name is now explicitly searched for in the overview information. * Fixed the source which is logged to the news log file for local postings when the local server is not listed in incoming.conf. A wrong name was used, taken amongst known peers. The source is now logged as "localhost". * Fixed a bug in the timecaf storage method: only the first 65535 articles could be retrievable in a CAF, though everything was properly stored. (A Crunched Article File contains all the articles that arrive to the news server during 256 seconds.) The storage token now uses 4 bytes to store the article sequence number for timecaf, instead of only 2 bytes. Thanks to Kamil Jonca for the bug report and also the patch. * Fixed a bug in both timecaf and timehash which prevented them from working on systems where short ints were not 16-bit integers. * When there is not enough space to write an entire CAF header, the timecaf storage manager now uses a larger blocksize. On 32-bit systems, the CAF header is about 300 bytes, leaving about 200 bytes for the free bitmap index (the remaining of a 512-byte blocksize). On 64-bit systems, the size of the CAF header could exceed 512 bytes, thus leaving no room for the free bitmap index. A 1 KB blocksize is then used, or a larger size if need be. * A new CNFS version has been introduced by Miquel van Smoorenburg in the CNFS header. CNFSv4 uses 4 KB blocks instead of 512 bytes, which more particularly makes writes faster. CNFSv4 supports files/partitions up to 16 TB with a 4 KB blocksize. Existing CNFS buffers are kept unchanged; only new CNFS buffers are initialized with that new version. * grephistory -l now returns the contents of the expires history field as well as the hash of the message-ID. Besides, when the storage API token does not exist, grephistory -v now also returns the hash of the requested message-ID. * The check on cancel messages when *verifycancels* is set to true in inn.conf has been changed to verify that at least one newsgroup in the cancel message can be found in the article to be cancelled. This new feature is from Christopher Biedl. The previous behaviour was to check whether the cancel message is from the same person as the original post, which is extremely easy to spoof; besides, RFC 5537 (USEPRO) mentions that "cancel control messages are not required to contain From: and Sender: header fields matching the target message. This requirement only encouraged cancel issuers to conceal their identity and provided no security". * The way the "/remember/" line in expire.ctl works has changed. History retention for an article was done according to its original arrival time; it is now according to its original posting date. Otherwise, unnecessary data may be kept too long in the history file. To achieve that, the HISremember() function in history API now expects a fourth parameter: the article posting time. Note that article expiration has not changed and is still based on arrival time, unless the -p flag is passed to expire or expireover, in which case posting time is used. * The default value for "/remember/" has changed from 10 to 11 because it should be one more than the *artcutoff* parameter in inn.conf, so that articles posted one day into the future are properly retained in history. * auth_krb5 has been rewritten by Russ Allbery to use modern Kerberos APIs. Note that using ckpasswd with PAM support and a Kerberos PAM module instead of this authenticator is still recommended. * A new -L flag has been added by Jonathan Kamens to makehistory so as to specify a load average limit. If the system load average exceeds the specified limit, makehistory sleeps until it goes below the limit. * As UTF-8 is the default character set in RFC 3977, "ctlinnd pause", "ctlinnd readers", "ctlinnd reject", "ctlinnd reserve", "ctlinnd throttle" and "nnrpd -r" commands now require the given reason to be encoded in UTF-8, so that it can be properly sent to news readers. The creator's name given to "ctlinnd newgroup" is also expected to be encoded in UTF-8. * The output of consistency checks for article storage and the history file no longer appears by default when "cnfsstat -a" is used. A new -v flag has been added to cnfsstat so as to see it. * The default path for TLS certificates has changed from *pathnews*/lib to *pathetc*. It only affects new INN installations or generations of certificates with "make cert". Besides, a default value has been added to *tlscapath* because it is required by nnrpd when TLS is used. * gzip(1) is now the default UUCP batcher in send-uucp instead of compress(1) because gzip is more widely available than compress, due to old patent issues. Note that there is no impact on decompression as it is handled by rnews. * cnfsheadconf now uses the Perl core module "Math::BigInt" rather than the deprecated bigint.pl library. When used without specifying a CNFS buffer, it now properly displays the status of all CNFS buffers. @ text @d1 1 a1 1 $NetBSD: patch-ai,v 1.6 2009/09/22 13:17:00 spz Exp $ d3 1 a3 1 --- include/inn/dbz.h.orig 2009-05-21 20:08:33.000000000 +0000 @ 1.6 log @Update of the INN package to the latest stable version (2.5.0). @ text @d1 1 a1 1 $NetBSD$ d3 2 a4 2 --- include/dbz.h.orig 2009-05-21 20:08:33.000000000 +0000 +++ include/dbz.h @ 1.5 log @regenerate patches with pkgdiff so they apply cleanly with devel/patch. @ text @d3 1 a3 1 --- include/dbz.h.orig 2004-01-08 09:47:19.000000000 +1100 @ 1.4 log @Update INN package to version 2.4.1. Major changes since version 2.3.x: - builtin IPv6 support - new configuration parser - completely rewriten "send-uucp" which replaces "sendbatch" @ text @d3 3 a5 3 --- include/dbz.h.orig 2004-01-07 23:47:19.000000000 +0100 +++ include/dbz.h 2004-06-02 13:02:04.000000000 +0200 @@@@ -38,7 +38,7 @@@@ @ 1.3 log @Apply patch pkgsrc-wip/newsx/news.inn.patch: Install header files for other packages (in particular, newsx). Bump PKGREVISION. Approved by tron@@ @ text @d3 4 a6 4 --- include/dbz.h.orig 2002-12-23 00:00:38.000000000 +0100 +++ include/dbz.h @@@@ -42,7 +42,7 @@@@ typedef struct { BOOL nonblock; @ 1.2 log @Update "inn" package to version 2.3.1. Changes since version 2.2.3: INN 2.3.0 represents a significant architectural change to INN, with a completely new internal overview interface, three new overview mechanisms, two new article storage mechanisms, and the elimination of quite a few old interfaces and old code. The NetBSD package furthermore includes IPv6 support and a new style startup script with backwards compatibility. @ text @d1 1 a1 1 $NetBSD: patch-ai,v 1.1 2000/08/17 14:00:28 wiz Exp $ d3 11 a13 20 --- installit.sh.orig Mon Dec 13 14:18:37 1999 +++ installit.sh @@@@ -95,7 +95,7 @@@@ ;; esac if ${ROOT} ; then - GROUP=`expr "$1" : '-g\(.*\)'` + GROUP=`expr "$1" : '-G\(.*\)'` CHGROUPIT=true fi ;; @@@@ -151,7 +151,7 @@@@ ;; esac if ${ROOT} ; then - OWNER=`expr "$1" : '-o\(.*\)'` + OWNER=`expr "$1" : '-O\(.*\)'` CHOWNIT=true fi ;; @ 1.1 log @USE_PKGLIBTOOL -> USE_LIBTOOL Added hack to post-build since the package's libtool recognizes more switches for the install program than the default libtool. @ text @d1 1 a1 1 $NetBSD$ @