From owner-freebsd-ruby@FreeBSD.ORG  Mon Jan 18 01:54:17 2010
Return-Path: <owner-freebsd-ruby@FreeBSD.ORG>
Delivered-To: ruby@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id E5FF91065695
	for <ruby@FreeBSD.org>; Mon, 18 Jan 2010 01:54:17 +0000 (UTC)
	(envelope-from spork@bway.net)
Received: from xena.bway.net (xena.bway.net [216.220.96.26])
	by mx1.freebsd.org (Postfix) with ESMTP id A310C8FC15
	for <ruby@FreeBSD.org>; Mon, 18 Jan 2010 01:54:17 +0000 (UTC)
Received: (qmail 74898 invoked by uid 0); 18 Jan 2010 01:27:37 -0000
Received: from unknown (HELO ?10.3.2.41?) (spork@96.57.144.66)
	by smtp.bway.net with (DHE-RSA-AES256-SHA encrypted) SMTP;
	18 Jan 2010 01:27:37 -0000
Date: Sun, 17 Jan 2010 20:27:36 -0500 (EST)
From: Charles Sprickman <spork@bway.net>
X-X-Sender: spork@hotlap.local
To: ruby@FreeBSD.org
Message-ID: <alpine.OSX.2.00.1001172021030.32117@hotlap.local>
User-Agent: Alpine 2.00 (OSX 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Cc: 
Subject: portupgrade errors on upgrade install
X-BeenThere: freebsd-ruby@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: FreeBSD-specific Ruby discussions <freebsd-ruby.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ruby>,
	<mailto:freebsd-ruby-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ruby>
List-Post: <mailto:freebsd-ruby@freebsd.org>
List-Help: <mailto:freebsd-ruby-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ruby>,
	<mailto:freebsd-ruby-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jan 2010 01:54:18 -0000

Howdy,

Occasionally I've been running into an issue when doing an upgrade on a 
port where the old port gets uninstalled and then the new port install 
fails.  So far the only fix is to manually deal with the deletion of the 
old port.

An example is probably the easiest way to demonstrate this:

--->  Build of shells/bash ended at: Fri, 15 Jan 2010 02:56:10 -0500 
(consumed 00:00:49)
--->  Updating dependency info
--->  Uninstallation of bash-4.0.33_2 started at: Fri, 15 Jan 2010 
02:56:10 -0500
--->  Fixing up dependencies before creating a package
--->  Backing up the old version

Looks good so far, port built without error, start the uninstall.

--->  Uninstalling the old version
--->  Deinstalling 'bash-4.0.33_2'
[Updating the pkgdb <format:bdb_btree> in /var/db/pkg ... - 66 packages 
found (-1 +0) (...) done]
--->  Uninstallation of bash-4.0.33_2 ended at: Fri, 15 Jan 2010 02:56:13 
-0500 (consumed 00:00:03)

Looks as if it has deinstalled the old bash...


--->  Installation of shells/bash started at: Fri, 15 Jan 2010 02:56:13 
-0500
--->  Installing the new version via the port
===>  Installing for bash-4.0.35
===>   bash-4.0.35 depends on shared library: intl - found
===>   Generating temporary packing list
===>  Checking if shells/bash already installed

It shouldn't be since we just uninstalled it (or did we?)

===>   bash-4.0.35 is already installed

Huh?
       You may wish to ``make deinstall'' and install this port again
       by ``make reinstall'' to upgrade it properly.
       If you really wish to overwrite the old port of shells/bash
       without deleting it first, set the variable "FORCE_PKG_REGISTER"
       in your environment or the "make install" command line.
*** Error code 1

Stop in /basejail/usr/ports/shells/bash.
*** Error code 1

Stop in /basejail/usr/ports/shells/bash.
** Command failed [exit code 1]: /usr/bin/script -qa 
/tmp/portupgrade20100115-40275-sdjqgj-0 env UPGRADE_TOOL=portupgrade 
UPGRADE_PORT=bash-4.0.33_2 UPGRADE_PORT_VER=4.0.33_2 make reinstall
--->  Updating dependency info
--->  Restoring the old version
--->  Keeping old package in '/var/ports/packages/All'
** Fix the installation problem and try again.
--->  Installation of shells/bash ended at: Fri, 15 Jan 2010 02:56:15 
-0500 (consumed 00:00:01)
--->  Upgrade of shells/bash ended at: Fri, 15 Jan 2010 02:56:15 -0500 
(consumed 00:00:55)
--->  ** Upgrade tasks 1: 0 done, 0 ignored, 0 skipped and 1 failed
[Updating the pkgdb <format:bdb_btree> in /var/db/pkg ... - 67 packages 
found (-0 +1) . done]
--->  Listing the results (+:done / -:ignored / *:skipped / !:failed)
         ! shells/bash (bash-4.0.33_2)   (install error)
--->  Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed
--->  Session ended at: Fri, 15 Jan 2010 02:56:17 -0500 (consumed 
00:01:03)

If it matters, this is in a jail.  This is 7.2 with portupgrade version 
2.4.6_3,2.

I've seen this pretty often, but have never been able to track down what's 
happening in that deinstall step.

Thanks,

Charles

___
Charles Sprickman
NetEng/SysAdmin
Bway.net - New York's Best Internet - www.bway.net
spork@bway.net - 212.655.9344


From owner-freebsd-ruby@FreeBSD.ORG  Mon Jan 18 11:08:32 2010
Return-Path: <owner-freebsd-ruby@FreeBSD.ORG>
Delivered-To: ruby@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id A52661065693
	for <ruby@FreeBSD.org>; Mon, 18 Jan 2010 11:08:32 +0000 (UTC)
	(envelope-from owner-bugmaster@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 7B2078FC15
	for <ruby@FreeBSD.org>; Mon, 18 Jan 2010 11:08:32 +0000 (UTC)
Received: from freefall.freebsd.org (localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id o0IB8WPO048916
	for <ruby@FreeBSD.org>; Mon, 18 Jan 2010 11:08:32 GMT
	(envelope-from owner-bugmaster@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.14.3/8.14.3/Submit) id o0IB8VOl048914
	for ruby@FreeBSD.org; Mon, 18 Jan 2010 11:08:31 GMT
	(envelope-from owner-bugmaster@FreeBSD.org)
Date: Mon, 18 Jan 2010 11:08:31 GMT
Message-Id: <201001181108.o0IB8VOl048914@freefall.freebsd.org>
X-Authentication-Warning: freefall.freebsd.org: gnats set sender to
	owner-bugmaster@FreeBSD.org using -f
From: FreeBSD bugmaster <bugmaster@FreeBSD.org>
To: ruby@FreeBSD.org
Cc: 
Subject: Current problem reports assigned to ruby@FreeBSD.org
X-BeenThere: freebsd-ruby@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: FreeBSD-specific Ruby discussions <freebsd-ruby.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ruby>,
	<mailto:freebsd-ruby-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ruby>
List-Post: <mailto:freebsd-ruby@freebsd.org>
List-Help: <mailto:freebsd-ruby-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ruby>,
	<mailto:freebsd-ruby-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jan 2010 11:08:32 -0000

Note: to view an individual PR, use:
  http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.


S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o ports/141183 ruby       ports/japanese/ruby-chasen update
s ports/140880 ruby       ports-mgmt/portupgrade: portversion confused with ezm3
o ports/140364 ruby       ports-mgmt/portupgrade-devel: #! line substitution is 
o ports/140273 ruby       ports-mgmt/portupgrade-devel chokes on bsdpan pkgs
o ports/140008 ruby       ports-mgmt/portupgrade: many papercut omissions on por
o ports/138796 ruby       [patch] - update converters/ruby-lv
o ports/137958 ruby       ports-mgmt/portupgrade fails with recursive dependency
o ports/137708 ruby       ports-mgmt/portupgrade: portupgrade -cRn is broken
s ports/134714 ruby       ports-mgmt/portupgrade deletes user data without quest
o ports/134182 ruby       ports-mgmt/portupgrade incorrectly handles manual reje
o ports/131111 ruby       ports-mgmt/portupgrade-devel: completely removes packa
o ports/129930 ruby       ports-mgmt/portupgrade - portinstall tries to install 
o ports/129891 ruby       ports-mgmt/portupgrade fails to recognize variations o
o ports/128881 ruby       ports-mgmt/portupgrade backtrace
o ports/127889 ruby       ports-mgmt/portupgrade detects spurious failures and s
o ports/127019 ruby       ports-mgmt/portupgrade does not recognize fail conditi
o ports/126140 ruby       ports-mgmt/portupgrade runtime error
o ports/125936 ruby       ports-mgmt/portupgrade -R fails if BUILD_DEP's are not
o ports/112818 ruby       ports-mgmt/portupgrade -a fails with database error

19 problems total.


From owner-freebsd-ruby@FreeBSD.ORG  Thu Jan 21 07:28:56 2010
Return-Path: <owner-freebsd-ruby@FreeBSD.ORG>
Delivered-To: ruby@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id E649B1065670
	for <ruby@freebsd.org>; Thu, 21 Jan 2010 07:28:56 +0000 (UTC)
	(envelope-from linimon@FreeBSD.org)
Received: from mail.droso.net (koala.ipv6.droso.net
	[IPv6:2001:6c8:6:c:20d:56ff:fe6f:f935])
	by mx1.freebsd.org (Postfix) with ESMTP id A17748FC23
	for <ruby@freebsd.org>; Thu, 21 Jan 2010 07:28:56 +0000 (UTC)
Received: from koala.droso.net (localhost.droso.net [IPv6:::1])
	by mail.droso.net (Postfix) with ESMTP id E05AE1CC3A
	for <ruby@freebsd.org>; Thu, 21 Jan 2010 08:28:55 +0100 (CET)
From: linimon@FreeBSD.org
To: ruby@freebsd.org
Message-Id: <20100121072855.E05AE1CC3A@mail.droso.net>
Date: Thu, 21 Jan 2010 08:28:55 +0100 (CET)
Cc: 
Subject: FreeBSD ports that you maintain which are currently marked broken
X-BeenThere: freebsd-ruby@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: portmgr-feedback@FreeBSD.org
List-Id: FreeBSD-specific Ruby discussions <freebsd-ruby.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ruby>,
	<mailto:freebsd-ruby-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ruby>
List-Post: <mailto:freebsd-ruby@freebsd.org>
List-Help: <mailto:freebsd-ruby-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ruby>,
	<mailto:freebsd-ruby-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jan 2010 07:28:57 -0000

Dear FreeBSD port maintainer:

As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as "broken" in their Makefiles.  In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments.  The most common problem is that recent versions
of -CURRENT include gcc4.2, which is much stricter than older versions.
The next most common problem is that compiles succeed on the i386
architecture (e.g. the common Intel PC), but fail on one or more
of the other architectures due to assumptions about things such as
size of various types, byte-alignment issues, and so forth.

In occasional cases we see that the same port may have different
errors in different build environments.  The script that runs on the
build cluster uses heuristics to try to 'guess' the error type to
help you isolate problems, but it is only a rough guide.

One more note: on occasion, there are transient build errors seen
on the build farm.  Unfortunately, there is not yet any way for this
algorithm to tell the difference (humans are much, much better at
this kind of thing.)

The errors are listed below.  In the case where the same problem
exists on more than one build environment, the URL points to the
latest errorlog for that type.  (By 'build environment' here we
mean 'combination of 6.x/7.x/-current with target architecture'.)

(Note: the dates are included to help you to gauge whether or not
the error still applies to the latest version.  The program
that generates this report is not yet able to determine this
automatically.)

portname:           x11-toolkits/ruby-panelapplet
broken because:     does not build with GNOME 2.26.
build errors:       none.
overview:           http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=ruby-panelapplet


If these errors are ones that you are already aware of, please
accept our apologies and ignore this message.  On the other hand, if
you no longer wish to maintain this port (or ports), please reply
with a message stating that, and accept our thanks for your efforts
in the past.

Every effort has been made to make sure that these error reports
really do correspond to a port that you maintain.  However, due to
the fact that this is an automated process, it may indeed generate
false matches.  If one of these errors fits that description,
please forward this email to the author of this software, Mark
Linimon <linimon@FreeBSD.org>, so that he can attempt to fix the
problem in the future.

Thanks for your efforts to help improve FreeBSD.

From owner-freebsd-ruby@FreeBSD.ORG  Thu Jan 21 07:30:18 2010
Return-Path: <owner-freebsd-ruby@FreeBSD.ORG>
Delivered-To: ruby@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 8F1741065696
	for <ruby@freebsd.org>; Thu, 21 Jan 2010 07:30:18 +0000 (UTC)
	(envelope-from linimon@FreeBSD.org)
Received: from mail.droso.net (koala.ipv6.droso.net
	[IPv6:2001:6c8:6:c:20d:56ff:fe6f:f935])
	by mx1.freebsd.org (Postfix) with ESMTP id 536D58FC22
	for <ruby@freebsd.org>; Thu, 21 Jan 2010 07:30:18 +0000 (UTC)
Received: from koala.droso.net (localhost.droso.net [IPv6:::1])
	by mail.droso.net (Postfix) with ESMTP id 8B1681CC96
	for <ruby@freebsd.org>; Thu, 21 Jan 2010 08:30:17 +0100 (CET)
From: linimon@FreeBSD.org
To: ruby@freebsd.org
Message-Id: <20100121073017.8B1681CC96@mail.droso.net>
Date: Thu, 21 Jan 2010 08:30:17 +0100 (CET)
Cc: 
Subject: FreeBSD ports that you maintain which are currently scheduled for
	deletion
X-BeenThere: freebsd-ruby@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: portmgr-feedback@FreeBSD.org
List-Id: FreeBSD-specific Ruby discussions <freebsd-ruby.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ruby>,
	<mailto:freebsd-ruby-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ruby>
List-Post: <mailto:freebsd-ruby@freebsd.org>
List-Help: <mailto:freebsd-ruby-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ruby>,
	<mailto:freebsd-ruby-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jan 2010 07:30:18 -0000

Dear FreeBSD port maintainer:

As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness.  Often,
this is due to a better alternative having become available and/or
the cessation of development on the existing port.  In some cases,
ports are marked for removal because they fail to build and install
correctly from their sources, or otherwise fail in operation.

The ports, and the reason and date that they have been scheduled
for removal, are listed below.  If no one has stepped forward before
that time to propose a way to fix the problems (such as via a PR),
the ports will be deleted.



portname:           x11-toolkits/ruby-panelapplet
description:        Ruby binding for libpanel-applet
maintainer:         ruby@FreeBSD.org
status:             BROKEN
deprecated because: has been broken for 7 months
expiration date:    2010-01-08
build errors:       none.
overview:           http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=ruby-panelapplet


If this problem is one that you are already aware of, please accept
our apologies and ignore this message.  On the other hand, if you no
longer wish to maintain this port (or ports), please reply with a
message stating that, and accept our thanks for your efforts in the
past.

Thanks for your efforts to help improve FreeBSD.