From owner-freebsd-ports@FreeBSD.ORG Mon Oct 20 06:59:06 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5844B11D; Mon, 20 Oct 2014 06:59:06 +0000 (UTC) Received: from mail-la0-x229.google.com (mail-la0-x229.google.com [IPv6:2a00:1450:4010:c03::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A417F304; Mon, 20 Oct 2014 06:59:05 +0000 (UTC) Received: by mail-la0-f41.google.com with SMTP id pn19so3383108lab.0 for ; Sun, 19 Oct 2014 23:59:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=jWklKKcXO0ltuUHBVCWMcZWhnt0Sob7GtCK4SkIpV5w=; b=0ud4LuHkunNktekKMGMw1ECAsH2b//dl5DEHn3dp2MnjkMjEZZuUl37zs8nPr4dUJy 1M7oExUrriVja68iCr4ZDB8bEhBqheTOpKBamIH19APKQ1S32fJX5Yc9gzWg1XUTuqRm SXB8cXVKW9EwEgVwD0CcQpWurCzNro4oUZt1zCtiOoBhHtQc/G52Xa+mOaoVvtVybGMx +GJWG9FjvpCa3abpJMLsqYx/v568c0J2+cFIlIbV7eQpi/FDWwp5x7Vu7KWNxVZDrB3V Cd0H1fzAsNE2mxw2UVq1FIMarZR2xI4+2xEOaSsLhiyx9W2gGbyPFPh0ddBz2aJbEoyI Mmkg== X-Received: by 10.112.16.195 with SMTP id i3mr25226906lbd.72.1413788343443; Sun, 19 Oct 2014 23:59:03 -0700 (PDT) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by mx.google.com with ESMTPSA id t2sm2976203lae.31.2014.10.19.23.59.01 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 19 Oct 2014 23:59:02 -0700 (PDT) Sender: Baptiste Daroussin Date: Mon, 20 Oct 2014 08:58:59 +0200 From: Baptiste Daroussin To: Andriy Gapon Subject: Re: latest freebsd:11:x86:64 repo and ruby 1.9 -> 2.0 Message-ID: <20141020065859.GI37244@ivaldir.etoilebsd.net> References: <544232F7.3060909@FreeBSD.org> <20141019220854.GH37244@ivaldir.etoilebsd.net> <5444ABC3.2040904@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="OfrWf2Fun5Ae4m0Y" Content-Disposition: inline In-Reply-To: <5444ABC3.2040904@FreeBSD.org> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-ports@FreeBSD.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Oct 2014 06:59:06 -0000 --OfrWf2Fun5Ae4m0Y Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Oct 20, 2014 at 09:29:23AM +0300, Andriy Gapon wrote: > On 20/10/2014 01:08, Baptiste Daroussin wrote: > > On Sat, Oct 18, 2014 at 12:29:27PM +0300, Andriy Gapon wrote: > >>> $ pkg upgrade Updating FreeBSD repository catalogue... FreeBSD > >>> repository is up-to-date. Updating poudriere repository catalogue...= =20 > >>> poudriere repository is up-to-date. All repositories are up-to-date.= =20 > >>> Checking for upgrades (24 candidates): 100% Checking integrity... done > >>> (1 conflicting) Checking integrity... done (0 conflicting) The > >>> following 24 packages will be affected (of 0 checked): > >>=20 > >> First, a minor nit: of 0 checked? > >>=20 > >>> Installed packages to be REMOVED: ruby-1.9.3.547_3,1 porttools-1.02= =20 > >>> newfile-1.0.14_4 hub-1.12.2 libchk-1.10.3 zfs-snapshot-mgmt-20090201_2 > >>=20 > >> Then the real problem, I do not want these packages to be removed exce= pt > >> for ruby-1.9.3.547_3,1. In other words, I want to keep using > >> zfs-snapshot-mgmt, libchk, hub and porttools. What should I do? > >=20 > > Just accept the upgrade and reinstall them they are there. we need to > > improve the solver to prevent that. >=20 > OK. This should work for me this time, but in general we can see how ann= oying > this could be if dozens of packages would be affected. Yes the problem is we have no way yet to know ruby-2.0 is an upgrade of rub= y-1.9 pkg 1.4 will know that. So it will be fixed automagically by pkg 1.4 regards, Bapt --OfrWf2Fun5Ae4m0Y Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlREsrMACgkQ8kTtMUmk6EwpIACfQb1SCqD5CDiQ0tSXBmbh5E1W JNIAn3c04WIK1WACoTbdGhfEX6dfi+2B =paRT -----END PGP SIGNATURE----- --OfrWf2Fun5Ae4m0Y--