Re: portupgrade problem?
Hi Bryan, Bryan Drewery: Sorry for the trouble. I just committed a fix. No worries - it's human effort after all. Thanks for your support keep up the good wojk! Jos Chrispijn ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
portupgrade problem?
I am having a problem with portupgrade; is anyone else seeing this?
=== Building package for portupgrade-2.4.11.2,2
Creating package /usr/ports/packages/All/portupgrade-2.4.11.2,2.tbz
Registering depends: ruby19-bdb-0.6.6_1 db41-4.1.25_4 ruby-1.9.3.448,1
libexecinfo-1.1_3 libffi-3.0.13 libyaml-0.1.4_2.
Registering conflicts: portupgrade-devel-*.
Creating bzip'd tar ball in
'/usr/ports/packages/All/portupgrade-2.4.11.2,2.tbz'
tar: libdata/ldconfig/portupgrade: Cannot stat: No such file or directory
tar: Error exit delayed from previous errors.
pkg_create: make_dist: tar command failed with code 256
*** [do-package] Error code 1
Stop in /usr/ports/ports-mgmt/portupgrade.
*** [reinstall] Error code 1
Stop in /usr/ports/ports-mgmt/portupgrade.
** Command failed [exit code 1]: /usr/bin/script -qa
/tmp/portupgrade20130923-47104-x5ofv env UPGRADE_TOOL=portupgrade
UPGRADE_PORT=portupgrade-2.4.11.1,2 UPGRADE_PORT_VER=2.4.11.1,2 make
BATCH=yes reinstall
--- Restoring the old version
--
Fill ALT_PKGDEP section in pkgtools.conf file for portupgrade to be
aware of alternative dependencies you use.
E.g.
ALT_PKGDEP = {
# Use the -nox11 port when another port depends on
category/portexample
'category/portexample' = 'category/portexample-nox11',
}
Note also, portupgrade knows nothing about how to handle ports with
different suffixes (E.g. -nox11). So you should explicitly define
variables (E.g. WITHOUT_X11=yes) for the ports in /etc/make.conf or
pkgtools.conf (MAKE_ARGS section) files.
--
** Fix the installation problem and try again.
[Updating the pkgdb format:bdb_btree in /var/db/pkg ... - 99 packages
found (-0 +1) . done]
** Listing the failed packages (-:ignored / *:skipped / !:failed)
! ports-mgmt/portupgrade (portupgrade-2.4.11.1,2) (install error)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: portupgrade problem?
Sorry for the trouble. I just committed a fix.
On 9/23/2013 8:06 PM, Brian W. wrote:
I am having a problem with portupgrade; is anyone else seeing this?
=== Building package for portupgrade-2.4.11.2,2
Creating package /usr/ports/packages/All/portupgrade-2.4.11.2,2.tbz
Registering depends: ruby19-bdb-0.6.6_1 db41-4.1.25_4 ruby-1.9.3.448,1
libexecinfo-1.1_3 libffi-3.0.13 libyaml-0.1.4_2.
Registering conflicts: portupgrade-devel-*.
Creating bzip'd tar ball in
'/usr/ports/packages/All/portupgrade-2.4.11.2,2.tbz'
tar: libdata/ldconfig/portupgrade: Cannot stat: No such file or directory
tar: Error exit delayed from previous errors.
pkg_create: make_dist: tar command failed with code 256
*** [do-package] Error code 1
Stop in /usr/ports/ports-mgmt/portupgrade.
*** [reinstall] Error code 1
Stop in /usr/ports/ports-mgmt/portupgrade.
** Command failed [exit code 1]: /usr/bin/script -qa
/tmp/portupgrade20130923-47104-x5ofv env UPGRADE_TOOL=portupgrade
UPGRADE_PORT=portupgrade-2.4.11.1,2 UPGRADE_PORT_VER=2.4.11.1,2 make
BATCH=yes reinstall
--- Restoring the old version
--
Fill ALT_PKGDEP section in pkgtools.conf file for portupgrade to be
aware of alternative dependencies you use.
E.g.
ALT_PKGDEP = {
# Use the -nox11 port when another port depends on
category/portexample
'category/portexample' = 'category/portexample-nox11',
}
Note also, portupgrade knows nothing about how to handle ports with
different suffixes (E.g. -nox11). So you should explicitly define
variables (E.g. WITHOUT_X11=yes) for the ports in /etc/make.conf or
pkgtools.conf (MAKE_ARGS section) files.
--
** Fix the installation problem and try again.
[Updating the pkgdb format:bdb_btree in /var/db/pkg ... - 99 packages
found (-0 +1) . done]
** Listing the failed packages (-:ignored / *:skipped / !:failed)
! ports-mgmt/portupgrade (portupgrade-2.4.11.1,2)(install error)
--
Regards,
Bryan Drewery
signature.asc
Description: OpenPGP digital signature
Re: subject=FreeBSD 6.1 gettext-0.16.1 portupgrade problem
On 3/31/07, Dino Vliet [EMAIL PROTECTED] wrote:
!--
@page { size: 8.5in 11in; margin: 0.79in }
P { margin-bottom: 0.08in }
--
Hi folks,
I saw this in
usr/ports/UPDATING:
20070318:
AFFECTS: users of
devel/gettext (ie: YOU)
AUTHOR: [EMAIL PROTECTED]
As a result of the upgrade to gettext-0.16.1, the shared library
version
of libintl has changed, so you will need to rebuild
all ports that
depend on gettext (ie: most of them,
sorry).
portupgrade -rf gettext
When I
issued this last command, portupgrade -rf gettext I get this
result:
--- Packages processed: 182 done, 0 ignored,
79 skipped and 7 failed
** Could not clean up temporary directory:
Directory not empty - /var/tmp/portupgradeRtIfghsG
So, what to
do next? Should I continue this command until all packages are
processed and none of them skipped and failed? Or can I continue
upgrading all my ports as from now?
I'm using freebsd 6.1 on a amd64 system.
Thanks in advanced
Dino
8:00? 8:25? 8:40? Find a flick in no time
with the Yahoo! Search movie showtime shortcut.
http://tools.search.yahoo.com/shortcuts/#news
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Go clean your /var/tmp directory manually...and I would run
portupgrade -rf --batch gettext
just from personal experience unless you want to wake up in the morning (or
get home from work) and find your session sitting at a prompt screen,
waiting for input.
--
--I'm not 'renting' my OS--
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
