From owner-freebsd-gnome@FreeBSD.ORG Fri Aug 9 17:29:52 2013 Return-Path: Delivered-To: gnome@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id EC89EBE2 for ; Fri, 9 Aug 2013 17:29:52 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-pd0-x234.google.com (mail-pd0-x234.google.com [IPv6:2607:f8b0:400e:c02::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C52F825BB for ; Fri, 9 Aug 2013 17:29:52 +0000 (UTC) Received: by mail-pd0-f180.google.com with SMTP id y10so806939pdj.39 for ; Fri, 09 Aug 2013 10:29:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=zDR+UDwoOTb3sRP7wApzo8nTXKxHUg3lF5TbKPA5a7o=; b=OsG+oy1mikXSV11TKOfE+awKa6vvEdNEJaeDQPAc1yz6wYQMhQmmNqVHBmsU4F9i0B vPOC2HA3pRjai/duvGZs9pdRLAWa77+yFNal6oqDIqV5WC6mSGbP2zwiljUrjJxbkU5b RIj/3UoFyUle9grqT7ZJTjvukfujwFDHTh1gFebUlgQrfWDALmxYN2Hh66cNrqVLGu72 hpiXmEuCRN0sPCXGK2KoJ+I1WlZkq+pK1FasEMExp/x5zL0Si80ZbhMk/FhqZMuuFuRH xaXdQA4PKV+TyeAJT0hFD6o72pe2qJDfqbJaGJwhAcSgeBRoHZlT+8Scm5SMLHqNFEvt 1b5g== MIME-Version: 1.0 X-Received: by 10.66.161.229 with SMTP id xv5mr1791028pab.87.1376069392477; Fri, 09 Aug 2013 10:29:52 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.67.14.66 with HTTP; Fri, 9 Aug 2013 10:29:52 -0700 (PDT) In-Reply-To: <5204A921.2050103@passap.ru> References: <5204A921.2050103@passap.ru> Date: Fri, 9 Aug 2013 10:29:52 -0700 X-Google-Sender-Auth: 8GG9UKJl5w7tjPw7QrrxRMC9K0A Message-ID: Subject: Re: UPDATING 20130731 gio-fam-backend From: Kevin Oberman To: Boris Samorodov Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD GNOME Users X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Aug 2013 17:29:53 -0000 On Fri, Aug 9, 2013 at 1:32 AM, Boris Samorodov wrote: > 09.08.2013 01:26, Kevin Oberman =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > > > I believe the note on in UPDATING 20130731 is incorrect, as least as fa= r > as > > portmaster. I don't use portupgrade, > > So do I. > > > so I can't say how it behaves. This > > also assumes that pkgng is not in use. > > > > If you do "portmaster -r gio-fam-backend" it will fail as it treats > glib20 > > as a replacement for gio-fam-backend. > > I doubt it. How a single command "portmaster -r gio-fam-backend" may > even know about glib20? And IMHO glib20 cannot be used as a > replacement. From PORTMASTER(8) about -r option: "is for > "rebuild the specified port, and all ports that depend on it." > gio-fam-backend is in MOVED, so portmaster and portupgrade will see glib20 as a replacement for gio-fam-backend. At least portmaster does not have the concept of a port merging into another. As a result, the "portmaster -f" will "update" gio-fam-backend" to glib20, but will not remove the existing glib20 port, but remove gio-fam-backend. (Ideally it would have deleted both, but it does not understand port merges.) The actual flow is: Build a list of ports depending on the port specified as an argument to '-r' starting with that port Check MOVED for the port specified as an argument to the '-r' option If found in MOVED, replace the specified port in the update list with the port in the MOVED file Build any build dependencies of that port that need updates (in this case that will usually mean gettext) Build the port (glib20) Delete the port being replaced (gio-fam-backend) Install the port (which fails as glib20 s already installed) If glib20 was deleted before the execution of "portmaster -r", the installation of glib20 will succeed Continue building all remaining ports in the list until complete There are a few added complexities, but this is the basic outline of the operation. It is similar for portupgrade, but I don't know that it is exactly the same. > > As a result, after building the new > > glib port, it tries to install it without deleting the old version and > > fails. This can be avoided by using the command "pkg_delete -f glib-2.\= *" > > before the instructions currently provided. > > > > Also, depending on the version of portmaster, gio-fam-backend may be > > automatically deleted by the portmaster -r command, so the pkg_delete o= f > > gio-fam-backend may fail. > > > > I have updated about a half dozen systems and all have required that th= e > > gio-fam-backend be deleted first to allow the portmaster -r to work. > > So did I (about a half dozen systems) and I did what is suggested at > UPDATING (rebuild ports with -r option and then remove gio-fam- > backend). Modulo some problems due to new ld properties at CURRENT > all went smooth. > > FYI: here is my .portmasterrc: > ----- > PM_SU_CMD=3D/usr/local/bin/sudo > BACKUP=3Dbopt > MAKE_PACKAGE=3Dgopt > DONT_SCRUB_DISTFILES=3DDopt > SAVE_SHARED=3Dwopt > ----- > > OK. I am baffled as to why it seems to work for you when uniformly failed for me. I can only note that all of my systems were running either 8.4, 9.1 or 9-STABLE. None used pkgng. None ran head. Some my have been running an outdated portmaster from back in May when I last updated ports on all of my production systems and I will admit that the 9-STABLE systems had to be cleaned up from an inconsistent state due to trying to update gio-fam-backend before Koop had the note in UPDATING. (Due to the attendant changes to the files in port/Mk, it was messy and may have affected the portmaster run, so the only systems to have the UPDATING instructions run cleanly were running the old portmaster. --=20 R. Kevin Oberman, Network Engineer E-mail: rkoberman@gmail.com