On Mon, 11 Jun 2012 17:31:10 -0700, Gary Kline 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 <rsimmo...@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 <kl...@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. is there any way I can grab
> > > just the ones that fail to compile? I'm down to fewer than 50
> > > ports.
> > > and wedged.
> >
> > You don't want to have /usr/ports out of sync. You want to let
> > cvsup/portsnap do it's thing. It's ideal to have the whole ports
> > collection up-to-date. You 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. You 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? Error output for the
> > ports you say are broken would be another good thing to supply.
>
> something in x11-toolkits/gtk20 blew up. SOOOO.
> lolngstoryshrt, I rebuilt from scratch [[ from the very
> beginning ]] around 2 hours ago. it Just died. here are
> the 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 \
> apple_red ./apple-red.png \
> gnome_foot ./gnome-foot.png \
> > test-inline-pixbufs.h \
> || (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#
>
> unless this port is known to be broken, I'll cvsup the ports
> tree.
If you're using csup instead of portsnap, you can get "faster"
updates of your ports tree (as portsnap transmits snapshots
which are less frequently taken).
In case you intendedly need to DOWNgrade a port (maybe because
the newer version doesn't work anymore, like the xzgv image
viewer), use the "portdowngrade" tool. As it as been mentioned,
having an out-of-sync ports tree is not recommended and can
lead to trouble.
So for example, if gtk20 fails, remove its cruft ("make clean"
for this port and maybe its dependencies; maybe also remove
the distfiles it downloaded), and update via CVS some hours
after the incident. It sometimes happens that the problems
magically resolve. :-)
It's recommended to restart port builds in a somewhat clean
environment, that's why it sometimes really helps to delete
files of a previous build.
Are you using a port management tool (e. g. portmaster) or do
you operate "on bare ports")?
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
