Date: Tue, 12 Jun 2012 00:34:44 -0400 From: Robert Simmons <rsimmons0@gmail.com> To: freebsd-questions@freebsd.org Subject: Re: any way to grab just One port to upgrade? Message-ID: <CA%2BQLa9DnGByn03r1SsXr18PU35m3G5i87cToBPmmnAPxdJZwxw@mail.gmail.com> In-Reply-To: <20120612003110.GA2394@thought.org> References: <20120611220232.GA29749@thought.org> <CA%2BQLa9D-LStjU7J%2BLnwPbE0muUsVBwqM4Myrp-kYKWTJ=q0cwg@mail.gmail.com> <20120612003110.GA2394@thought.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jun 11, 2012 at 8:31 PM, Gary Kline <kline@thought.org> wrote: > On Mon, Jun 11, 2012 at 06:14:52PM -0400, Robert Simmons wrote: >> Date: Mon, 11 Jun 2012 18:14:52 -0400 >> From: Robert Simmons <rsimmons0@gmail.com> >> Subject: Re: any way to grab just One port to upgrade? >> To: freebsd-questions@freebsd.org >> >> On Mon, Jun 11, 2012 at 6:02 PM, Gary Kline <kline@thought.org> wrote: >> > it is easy to cvs or cvsup ports and get a whole slew of ports in >> > /usr/ports/distfiles, but too often, using portmaster [or another >> > tool], I'll have only one of two ports that fail because they are >> > either 1) broken, or 2) out of date. =A0is there any way I can grab >> > just the ones that fail to compile? =A0I'm down to fewer than 50 >> > ports. >> > and wedged. >> >> You don't want to have /usr/ports out of sync. =A0You want to let >> cvsup/portsnap do it's thing. =A0It's ideal to have the whole ports >> collection up-to-date. =A0You may want to start with a clean slate and >> cvsup/portsnap a fresh copy of the ports collection if you think that >> something is amiss. =A0You can make a backup of /usr/ports for peace of >> mind too. >> >> Also, can you please supply exactly what ports you're talking about >> and what commands you are running to upgrade? =A0Error output for the >> ports you say are broken would be another good thing to supply. > > =A0 =A0 =A0 =A0something in x11-toolkits/gtk20 blew up. =A0SOOOO. > =A0 =A0 =A0 =A0lolngstoryshrt, I rebuilt from scratch [[ from the very > =A0 =A0 =A0 =A0beginning ]] around 2 hours ago. =A0it Just died. =A0here = are > =A0 =A0 =A0 =A0the last 20 lines:: > > > gmake[2]: Leaving directory > `/usr/ports/x11-toolkits/gtk20/work/gtk+-2.24.6/modules' > Making all in demos > gmake[2]: Entering directory > `/usr/ports/x11-toolkits/gtk20/work/gtk+-2.24.6/demos' > /usr/local/bin/gdk-pixbuf-csource --raw --build-list =A0 =A0 =A0 =A0 =A0 = =A0\ > =A0 =A0 =A0 =A0apple_red =A0./apple-red.png =A0 =A0 =A0\ > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0gnome_foot ./gnome-foot.png =A0 =A0 \ > =A0 =A0 =A0 =A0> test-inline-pixbufs.h =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 \ > || (rm -f test-inline-pixbufs.h && false) > failed to load "./apple-red.png": Couldn't recognize the image file > format for file './apple-red.png' > gmake[2]: *** [test-inline-pixbufs.h] Error 1 > gmake[2]: Leaving directory > `/usr/ports/x11-toolkits/gtk20/work/gtk+-2.24.6/demos' > gmake[1]: *** [all-recursive] Error 1 > gmake[1]: Leaving directory > `/usr/ports/x11-toolkits/gtk20/work/gtk+-2.24.6' > gmake: *** [all] Error 2 > *** Error code 1 > > Stop in /usr/ports/x11-toolkits/gtk20. > *** Error code 1 > > Stop in /usr/ports/x11-toolkits/gtk20. > root@ethic:/tmp# > > =A0 =A0 =A0 =A0unless this port is known to be broken, I'll cvsup the por= ts > =A0 =A0 =A0 =A0tree. That may not be necessary. I'm building gtk20 on a freshly installed virtual machine with a freshly portsnap'd ports tree. I noticed the following in the CVS logs: CVS log for ports/x11-toolkits/gtk20/Makefile Revision 1.256: download - view: text, markup, annotated - select for diffs Fri Jun 1 05:25:47 2012 UTC (10 days, 22 hours ago) by dinoex Branches: MAIN CVS tags: HEAD Diff to: previous 1.255: preferred, colored Changes since revision 1.255: +1 -1 lines - update png to 1.5.10 Since png just changed, and the error you encountered is "failed to load "./apple-red.png": Couldn't recognize the image file", I think you may have run into a bug. I'll find out in the morning when the build is done.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BQLa9DnGByn03r1SsXr18PU35m3G5i87cToBPmmnAPxdJZwxw>