http://ctan.org/license/gfsl
Since this is basically the LaTeX Project Public License with one clause
removed, add it to the default acceptable licenses.
(lppl is fine with both OSI and FSF and already allowed.)
Given that libarchive is built with large file support, pkg_install
needs it too. Otherwise libarchive and pkg_install may see different
definitions of types such as struct stat, resulting in a runtime
failure on some platforms (especially Darwin 9):
% bmake package
=> Creating binary package /usr/pkgsrc/pkgtools/pkg_install/work/.packages/pkg_install-20141227.tgz
pkg_create: cannot write to archive: tar format cannot archive this (type=00)
The reason why this was unnoticed until now is that libarchive's
"configure" has just been regenerated with Autoconf 2.69. Prior to
2.69, AC_SYS_LARGEFILE did nothing significant on Darwin so there was
no actual inconsistency between libarchive and pkg_install, which was
just coincidental.
prevents us from attempting to link the inplace libarchive against itself.
Fixes build on systems which do not include a native libarchive, and avoids
possible issues on systems which do.
Tested on SmartOS (no native libarchive) and OS X in both builtin and pkgsrc
configurations. Ok joerg@.
don't redefine 'pkg_info' if it already exists.
This is notably for pkg_rolling_replace -u in case pkg_install
was revbump'd and openssl happens to be in PKG_DEFAULT_OPTIONS.
signature_archive were not initialized properly, therefore randomly failing
in the verify_signature_read_cb() callback.
Partly closes PR pkg/48194; pkgsrc needs to be updated as well.
"please commit" agc@
XXX pull-up to netbsd-6
Remove incorrect return value when in force mode, which was causing pkg_add
to exit with failure even though the operation completed successfully. This
also fixes the case where 'pkg_add -uf' would leave an update in an
inconsistent state.
itself. Copied from similar code in pkg_delete.
This fixes the issue when an +INSTALL script fails but the pkgdb directory
couldn't be removed, leading to an inconsistent state.
* bare `zu' modifier is used, it should be replaced with `PRIzu` instead.
Fixes crash with `pkg_admin rebuild' on platforms missing %z support,
PR pkg/48070.
if no eol is found in the string we set "next" to NULL, assign it
to "buf" and then check the loop condition by dereferencing it - which
does not work well.
Change the loop condition to first check for buf == NULL.
pkg_info(1) - from Bug Hunting in PR pkg/47328. The following text is
taken from Bug's PR:
The pkg_info(1), pkg_admin(1), and pkg_install.conf(5) man pages
from pkgsrc' pkgtools/pkg_install package contain errors, have
inaccurate / incomplete / illogically ordered descriptions, have
incorrect macro usages / macro errors, miss an option description
(`-h', for pkg_info(1)), and / or contain other imperfections.
In short: these man pages can use a big correction update.
Additionally, the `usage' message in main.c from pkg_info(1) contains
an incorrect option order.
that we prefer pkgsrc for OpenSSL. While the latter doesn't actually work
yet, it's better that we are deterministic about this and do not pick up
the system OpenSSL regardless.
- Explicitly stat(2) if mkdir failed. errno detection doesn't work e.g.
on Solaris (PR 45289)
- Provide a stable order for package names that only differe in the base
name, not the version number.
Problem analysis from Anthony:
On Wednesday, at 23:52, Anthony Mallet wrote:
> # rm -rf ~tmp && mkdir ~/tmp
> # pkg_add -K ~/tmp/var/db/pkg -p ~/tmp /usr/pkgsrc/packages/All/digest-20080510.tgz
> # pkg_add -U -K ~/tmp/var/db/pkg -p ~/tmp /usr/pkgsrc/packages/All/digest-20080510.tgz
> pkg_delete: Couldn't remove package directory in `/home/tho/tmp/var/db/pkg/digest-20080510'
> Also, the dir var/db/pkg/digest-20080510.xxxxxxx is never cleaned.
>
> The problem apparently is that pkg_delete finds some stalled NFS entries
> (.nfs*) in the var/db/pkg/digest-20080510 dir, so it does not delete the
> directory. Is this due to pkg_add not correctly closing file descriptors before
> exec'ing pkg_delete? For instance, I really don't understand the logic in
> check_already_installed() (add/perform.c:375) regarding the open() of +CONTENTS
> which is almost never closed (and never used as well...). Shouldn't this be
> closed before running pkg_delete?
ktrace shows that the +CONTENTS file is open() by pkg_add, I believe this is in
check_already_installed(), add/perform.c:381. Then pkg_delete is run and when
it comes to deleting the pkgdir entry, it finds that .nfs file and aborts.
Bump version to 20110805
