From owner-freebsd-ports@FreeBSD.ORG Mon Dec 24 13:13:50 2012 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B0CAF468 for ; Mon, 24 Dec 2012 13:13:50 +0000 (UTC) (envelope-from jeffreybouquet@yahoo.com) Received: from nm16-vm7.bullet.mail.gq1.yahoo.com (nm16-vm7.bullet.mail.gq1.yahoo.com [98.137.177.240]) by mx1.freebsd.org (Postfix) with ESMTP id 64F418FC0C for ; Mon, 24 Dec 2012 13:13:49 +0000 (UTC) Received: from [98.137.12.189] by nm16.bullet.mail.gq1.yahoo.com with NNFMP; 24 Dec 2012 13:13:43 -0000 Received: from [98.137.12.223] by tm10.bullet.mail.gq1.yahoo.com with NNFMP; 24 Dec 2012 13:13:43 -0000 Received: from [127.0.0.1] by omp1031.mail.gq1.yahoo.com with NNFMP; 24 Dec 2012 13:13:43 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 144746.30520.bm@omp1031.mail.gq1.yahoo.com Received: (qmail 64165 invoked by uid 60001); 24 Dec 2012 13:13:43 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1356354823; bh=vxyoccBCEjF9ckKZYfLaaYntQJWKwiRvuY8f9t6xbq4=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=DEWSBUIESbjzYbYNE9k0oWxGNxMAvm899aOQLgkFxHY0wgp4ppR0f60oiEou815B5PuMyqG3GQhnb4cqniAiMaV+74Z+l8BICZSNjIBnYMMCxrBFuEjSDKxMQyMbRmLNJ3zHca09VA7te4qXNrIpF1OQeMM4MLMLSvBhpKDR/ew= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=boaCqs2VX3KMCJcUjvDrQn0aUr0EXlejN/iDWZ/dqyB4ihz8LFEoCUNJZKhR8tSUUvFntl016X7LsOITDi3vqBK+q7o9Czdl4FI2/EUM+pJZNGWvcRfvLJwzyATGzAoopUADQOe8LF5bQ0Y6gXuqiX4cp7Bjc3NS26q9QMHpsaQ=; X-YMail-OSG: 2RSWM_gVM1ldyilUN51.wEF5tJaS_lA1cbsSv.lWydUtX.m u1eT8dgQp3Z6KYHe8GQzSp4cGxJd2s1AKUE1ghQ7pr4Ih5IqA89dG1FGhfgh .XdlxakvAh2Vt69AoFIV0mBaWlvEUHAqZoXuHERsiWy7IFM1hRD.llRh6irf BRe3apQ3bUDdzSeHFzgSMOqQWnCU1qDixWUhotCo8a9rbjAngG5jliEPxWrW eFd.nn8CMPdGW_01PR7NtZWBGgnxLgHENCcN2La2pL0JzS7VGJHP4qIxWOwe qEJKiAYndF1G_CC.t1cQitEnnEASOvW2TU2wMp13Oo9zHdzC4Ma_NZ2FDHcp GMDSN3MRTBX45g39DIDQjgRDsk42XVuqb8dLfgM6NOW750hOuYAgMW3LFloe 2ixn7V5a0N.UwGPLIIl482B_MHmIjtJW7Kvxpi7rHOEdWeUntg6_z0zOD_vh i_HmfI9PRvkv4SYC.8qyTIGcdX00rpoJxHDbQJxhLKFkpreVhYYd.YwkCZiS sGG4m Received: from [66.92.43.99] by web164004.mail.gq1.yahoo.com via HTTP; Mon, 24 Dec 2012 05:13:42 PST X-Rocket-MIMEInfo: 001.001, U29ycnkgZm9yIHRoZSBmb3JtYXR0aW5nLsKgIChUaGUgb3RoZXIgd2VibWFpbCBJIGNvdWxkIHVzZSBpcyBldmVuIG1vcmUgcHJvYmxlbWF0aWMpLg0KDQotLS0gT24gU3VuLCAxMi8yMy8xMiwgQmVhY2ggR2VlayA8bGFiZWFjaGdlZWtAZ21haWwuY29tPiB3cm90ZToNCg0KRnJvbTogQmVhY2ggR2VlayA8bGFiZWFjaGdlZWtAZ21haWwuY29tPg0KU3ViamVjdDogUmU6IFVwZ3JhZGluZyBwb3J0cyBwcm9ibGVtIHdpdGggcG9ydHVwZ3JhZGUocGtnbmcpDQpUbzogZnJlZWJzZC1wb3J0c0BmcmVlYnNkLm9yZw0BMAEBAQE- X-Mailer: YahooMailClassic/15.1.2 YahooMailWebService/0.8.129.483 Message-ID: <1356354822.41996.YahooMailClassic@web164004.mail.gq1.yahoo.com> Date: Mon, 24 Dec 2012 05:13:42 -0800 (PST) From: Jeffrey Bouquet Subject: Re: Upgrading ports problem with portupgrade(pkgng) To: freebsd-ports@freebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Dec 2012 13:13:50 -0000 Sorry for the formatting.=A0 (The other webmail I could use is even more pr= oblematic). --- On Sun, 12/23/12, Beach Geek wrote: From: Beach Geek Subject: Re: Upgrading ports problem with portupgrade(pkgng) To: freebsd-ports@freebsd.org Date: Sunday, December 23, 2012, 1:05 PM On Dec 22, 2012 2:15 PM, "Beach Geek" wrote: > > System: FreeBSD/i386 10-current, base/head(src)=3Dr244363, ports/head=3Dr309344. > > I upgraded to r244363 from an Oct 3rd(ish) version. Followed ports/UPDATING for pkgng to edit make.conf and convert pkgdb.db. > > I'm now trying to update my ports (from tree, not pkgs), and I get: > >=A0 =A0=A0=A0# portupgrade -ae >=A0 =A0=A0=A0USING PKGNG >=A0 =A0=A0=A0Stale dependency: ORBit2-2.14.19 --> glib-2.28.8_4 -- manuall= y run 'pkgdb -F' to fix, or specify -O to force. > >=A0 =A0=A0=A0# pkgdb -F USING PKGNG pkgdb -F not supported with PKGNG yet.= Use 'pkg check' directly. > >=A0 =A0=A0=A0# pkg check -d (also tried pkg check -d -a) >=A0 =A0=A0=A0# > > Running portupgrade -ae gives same message as before. > > Went to port tree, upgraded glib with 'make deinstall reinstall clean'. Then.... >=A0 =A0=A0=A0# pkg info glib glib-2.28.8_5 Some useful routines of C progr= amming (current stable version) > > Run portupgrade -ae...... same message. > > Could someone point me in the right direction... > > If I'm misunderstanding the man & wiki pages, please explain (I'll even wear the pointyhat). > > Thanks, BG An update..... 4 servers have the problem in my previous post, and I've yet to find a way to use portupgrade. Only answers I've received were to use packages via pkgng. (Not an option). For the other 9 servers, I tried it a little differently. =A0 =A0 -=A0 switch to pkgng =A0 =A0 -=A0 svn base and ports =A0 =A0 -=A0 upgrade base =A0 =A0 -=A0 upgrade ports with portupgrade. Worked fine for 8 of 9. Will be rolling the 5 broke servers back (yes, we have bkups) ;) Will leave the 8 working ones running pkgbg, and see how it goes. Still wondering, how to repair the database w/o pkgfb -F so portupgrade will work? And as I understand,=A0 poudriere must be used instead of portupgrade to create packages? Thanks, BG _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" I would hope that pkgng not be the default before someone writes a huge flo= wchart pointing out all or most all of the here-to-there scenarios, for ins= tance if one uses a -devel version of some /devel/ port suddenly, some packages brea= k, for instance some machines run v8 some run v10, which ports won't be in = the official build cluster and would commonly need to be built locally, and a s= lew of other issues which may be slowly added to the flowchart as the years go by,= so that questions would be fewer all around.=A0=A0 (Hoping also for a GEOM= flowchart, a CUPS flowchart, ... but that is off topic for this email...)= =20 BTW I've a methodology to rapidly dispense with unknown-but-need-upgrading = dependency upgrading (which just uncovered a slew of ports which won't buil= d, most with a similar error) and it heavily relies upon the /var/db/pkg/ s= tructure for ease of use.=A0 I also wish that an adjunct to the pkg(ng) include an optio= n for that structure so that that ease of use is not abstracted in a yet unknown way. If this will all be minor issues vs actual implementation of a v10 default = pkg system, I apologize in advance.=A0 (After all, most or all of the ports= which won't=20 currently build here I seldom if ever actually have time to use...)=20 J. Bouquet=20