An unpleasant bug was fixed when pkgdb could accidently remove some
dependencies in +CONTENTS files. It's recomented to run pkgdb -L once
after upgrade to fix dependencies list. See UPDATING file.
Reported and tested by: Randy Pratt <bsd-unix_AT_earthlink.net>
Most visible changes are:
* Database files locking. Only one process can write to them
in the same time.
* pkgdb -F is more smart now and takes OPTIONS, make.conf and
pkgtools.conf settings into account.
Moreover:
* Many bugs fixed.
* Many code refactored.
(MFD - Merge From Developing)
* Fix a bug with a time delta. When build took over 24 hour.
* Allow origins in ALT_PKGDEP.
* Add -e (--emit-summaries) option to show summary messages.
* Fix portupgrade working when stdin is closed. [1]
- Get back sf.net to MASTER_SITES
- Add CONFLICTS with portupgrade-devel
PR: ports/99179 [1]
Submitted by: Hannes Hauswedell <hannes.hauswedell_at_gmail.com>
It's exactly like 2.1.3 but without summary messages and
fixed bug when BDB4 was defined but tried only bdb1 driver and
fall back to dbd driver.
- Add an option WITH_BDB1. Both BDB1 and BDB4 options can be off.
Ruby dbd driver will use in the case.
* Add -e (--emit-summaries) option and show summary messages only when
the option defined or verbose mode is on. [1]
* Allow origins in ALT_PKGDEP. This announced in pkgtools.conf
but did not work really. [2]
* Run 'make config' before all operations unless -j (--jet-mode)
option specified. [3]
* Add lock on operations with pkgdb.db. Now you can safe run a few
portupgrade(1).
* Incorrectly calculated upgrade time when it is more 24 hours. [4]
* Other fixes and impovements.
PR: ports/99086 [4]
Reported by: Doug Poland <doug at polands.org> [3,4]
Requested by: many [1]
Submitted by: skv [2]
o Add ALT_INDEX array to pkgtools.conf. The array holds additional
INDEX files. Useful for local categories.
o Add to pkgtools.conf a new dirrective: include_hash('glob').
It downloads keys and values (splitted by '=>') from files
coincided with 'glob' and returns a filled hash. The glob is
related to PREFIX. [1]
o Add a summary messages on each upgrade/install transaction:
how many tasks and how many task done. [2]
o Make portupgrade(1) with -D option really remove a broken distfile.
But it works only if FETCH_CMD set to use fetch(1) (it's default). [3]
o Bugs fixes
Requested by: skv [1]
netchild [2]
Andriy Gapon <avg at icyb.net.ua> [3]
o Really fix *_rc_scripts. The last fix was uncomplited.
o Set both make argument and environment variable to PORT_UPGRADE=yes.
It makes possible a port or a package (via install/deinstall scripts)
to detect if it builds/installs/deinstalls under portupgrade(1) [1]
o Add to pkgtools.conf a new directive: include_eval('file')
The file will included and evaluated in the place where encountered.
The file path looking inside of PREFIX. [2]
o Add to pkgtools.conf ALT_MOVED. The array holds alternate MOVED file.
E.g. for files in EXTRA_CATEGORIES. [3]
o Allow install port by origin. E.g. portinstall lang/ruby18
o Make pkgdb offer install a stale dependency before selecting it from
installed. [4]
- Add own mirror to prevent delay while distfile appears on MASTER_SITE_LOCAL.
Requested by: skv [1,2,3], kris [4]
o Fix -O that should force ignoring dependency errors,
but really did not work [1]
o Add PKG_BACKUP_DIR environment variable where specified
a directory where will keep saved packages (-b).
Default: PKG_PATH (PORTSDIR/packages/All) [2]
o Add MAKE_ENV in pkgtools.conf that is like MAKE_ARGS but
allows to set environment variables for ports [3]
o Fix pkg_fetch(1) to guess a right source directory for
download (All or Latest). It works in much more cases now [4]
And make a notice for using of '@' in package name more clean.
o *_rc_scripts internal procs don't recognize RC-scripts without .sh.
It's wrong for 6.0+ [5]
o Fix pkgdb -s [6]
o Add firefox in a browser list in portcvsweb(1)
o Revive NEWS file
PR: ports/56301 [1]
ports/81454 [2] (based on)
ports/92896 [3]
ports/94054 [4]
ports/95775 [5]
ports/96832 [6]
Reported by: Roman Neuhauser <neuhauser at sigpipe.cz> [1]
Fernan Aguero <fernan at iib.unsam.edu.ar> [3]
Andrew Webster <awebster at connectalk.com> [4]
Rong-En Fan <rafan at infor.org> [5]
Richard Brooksby <rb at ravenbrook.com> [6]
Submitted by: KOMATSU Shinichiro <koma2 at lovepeers.org> [2]
- Update to 2.1.0
o rewrite version checking. Now it's compliant with pkg_version(1) algorythm
o fix shebangs in test/*
o add test in test_pkgversion.rb from test-pkg_version.sh
o fix test_pkgdb.rb
o fix pointyhat URL in pkgtools.conf and pkgtools.rb
o make comparisons when updates from packages. It compared package names
instead versions. It gives a weird results when port was renamed
(eg. mozilla-firebird -> firefox) [1]
o don't show a warning about origin changing when origins are the same. [2]
It rids us from messages like:
Package origin of 'pan' has been changed: 'news/pan' -> 'news/pan'
PR: ports/62990 [1], ports/98153 [2]
Submitted by: Leland Wang <llwang at infor.org> [1]
tobez [2]
Approved by: maintainer (silence for a month, no activity seen for 4 monthes)
daichi (blessed)
ports (silence)
a number open PRs from 2003 year
Inspired by: az
* portversion(1) also reads MOVED and trace origin change,
and, when invoked with "-v", displays the new origin.
Example:
% portversion -v screen
screen-4.0.2_2 < needs updating (port has 4.0.2_3) (=> 'sysutils/screen')
* Add "--ignore-moved" to portupgrade(1) and portversion(1).
When invoked with this option, both programs totally ignore MOVED.
If you encounter strange behaviour of these programs, try this out.
* Add IGNORE_MOVED option to pkgtools.conf.
This can be used to selectively ignore MOVED by pkgs.
See pkgtools.conf.sample for details.
* Keep the order of MOVED entries, and do not trace back to old entries.
Previously, when encounters the following entries,
editors/emacs|editors/emacs19|2004-03-20|emacs 19.x moved to a non-default port location
editors/emacs21|editors/emacs|2004-03-20|emacs 21.x moved to default port location
portupgrade traces as "editors/emacs21" -> "editors/emacs" -> "editors/emacs19".
I thought this behavior should not be what we want to, so added this change.
PR: ports/91272
Submitted by: KOMATSU Shinichiro <koma2@lovepeers.org> (maintainer)
Thank you for reporting. I also discovered this problem a few hours ago.
The source of this trouble is that the following line exists in MOVED,
lang/php4|lang/php4|2003-05-22|re-separated from www/mod_php4
where "moved from" and "moved to" is the same, but portupgrade
does not check this case and infinite loop occurs.
Fix to this problem will be in the next portupgrade release,
but in the meanwhile, whould you commit the following patch,
please?
PR: ports/91209
Submitted by: KOMATSU Shinichiro <koma2@lovepeers.org>
(1) Change the versioning scheme of portupgrade.
portupgrade now becomes 2.0.0!
(2) Add FreshPorts support to portcvsweb(1).
You can view CVS history via FreshPorts instead of CVSweb
by using "portcvsweb -F". See the man page of portcvsweb(1) for details.
(3) If the change of the origin is written in MOVED,
portupgrade reads and chases it.
You no longer need to supply the origin of the new pkg by "-o" option.
Example:
When ftp/wget-devel is moved to ftp/wget, previously you had to run,
% portupgrade -o ftp/wget wget
Now, just run
% portupgrade wget
and portupgrade will do what you want to do.
(4) Try to guess the pkg to be upgraded, when no pkgname is supplied
as a command line argument.
This can be done only when the current directory is under $PORTSDIR.
Example:
Running
% cd /usr/ports/ftp/wget
% portupgrade
will upgrade ftp/wget.
(5) The frequency of INDEX generation on official site is now sufficient,
recommend to run "portsdb -F" (fetch INDEX from official site)
instead of "portsdb -U" (make INDEX by yourself) in portsdb(1). [1]
PR: ports/91164
Submitted by: KOMATSU Shinichiro <koma2@lovepeers.org> (maintainer)
Pointed out by: Enrique Matias <cronopios at gmail dot com> [1]
(1) For years, I have experienced that portupgrade sometimes
runs very slow. After some investigation, I found that
"pkgdb -aF" is invoked from portupgrade or other programs
(such as portversion) without having sufficient privilege
to modify /var/db/pkg/, and that error is not caught by the
caller program, and "pkgdb -aF" is invoked repeatedlly.
So, I fixed the following things:
- When pkgdb internally invoked from other program exits
with error, make the caller program also exit with error.
- Display the error messages of pkgdb that run internally
from other program.
When portupgrade or other programs die with the following error,
** You do not own /var/db/pkg. (use -f to force or run as root)
Command failed [exit code 1]: /usr/local/sbin/pkgdb -aFQ
please run "pkgdb -aF" as the user that owns /var/db/pkg (usually root).
(2) Make new tarball that contains the above fix and all
patches in files/. Bump PORTVERSION to 20051204 and change
MASTER_SITES.
PR: ports/89917
Submitted by: KOMATSU Shinichiro <koma2@lovepeers.org>
(1) Do not change default dependency (depend on ruby-bdb1),
since ruby-bdb (BDB >= 2) support is not so tested.
(2) Thus, no PORTREVISION bump.
- a little Makefile change for portlint clean
PR: ports/82000
Submitted by: Alexander Novitsky <alecn@server.v42of.icc-vvd.ru>
Reviewed by: KOMATSU Shinichiro <koma2@lovepeers.org> (maintainer)
fix minor documentation issues with the portsclean(1) manpage.
1. In the SYNOPSIS, the -L option is excluded.
2. In the description for the -Q option, an example of the -QQ option
is not given and since the other descriptions do this,
it looks nicer and is easier to read.
PR: ports/82666
Submitted by: KOMATSU Shinichiro <koma2@lovepeers.org> (maintainer)
Pointed out by: Jason E. Hale <jhale@bluebottle.com>
- change portupgrade-port-maintainership to KOMATSU Shinichiro-san
<koma2@lovepeers.org>
knu gave me approval to change portupgrade-port-maintainership to
KOMATSU-san. He is busy attending to his work. He gave me approval to
change some of his pr's responsible to me. I'll get work around
portupgrade pr with KOMATSU-san.
Submitted by: koma2@lovepeers.org
Approved by: knu
every run, which also makes portversion(1) works for non-root users
again. This is done by simply having the flag file in /var/db/
(thanks to pav for the suggestion).
- While here anyway, fix some make warnings during install on FreeBSD 6.
PR: ports/81088
Reported by: many
Tested by: Yoshiaki Kasahara <kasahara@nc.kyushu-u.ac.jp>
Approved by: erwin (mentor)
