tcl84 port upgrade fails in test
I have been unable to update tcl8.4 on my laptop running -current. I have one other system running -current, but it installed the upgrade correctly. It compiles without error, but if fails in the tests. All of the errors were socket connection failure and included http, httpold, io, and socket. he test seemed to hang after socket 7.4. The network is operating fine on this system, so I have no idea what the problem might be. Has anyone else seen this? -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: tcl84 port upgrade fails in test
> Date: Mon, 3 Jul 2006 02:33:16 -0700 > From: "Jack L." <[EMAIL PROTECTED]> > > I have the same problem, all my boxes are running 6.1-STABLE but some > install, some wont. > > On 7/3/06, Matthias Andree <[EMAIL PROTECTED]> wrote: > > "Kevin Oberman" <[EMAIL PROTECTED]> writes: > > > > > I have been unable to update tcl8.4 on my laptop running -current. I > > > have one other system running -current, but it installed the upgrade > > > correctly. It compiles without error, but if fails in the tests. > > > > Same here on RELENG_6 (aka. -STABLE), > > although I haven't checked the details or looked closer at the failing > > tests. > > > > -- > > Matthias Andree > > ___ > > freebsd-ports@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > > I found the problem(s) with this. 1. My firewall was blocking some tests. Some tests are run to loopback, but others run the the address of the hostname. My firewall was blocking the latter. Disabling the firewall fixed that one. 2. My hostname has multiple A records in DNS as the laptop may be plugged into as well as per-location names, but "hostname" is a constant and I has a 50-50 chance of getting the right one. I guess the previous attempt to install with the firewall disabled lost the coin-flip. I added an entry to /etc/hosts for my system where it was REALLY connect5ed and disabled the firewall. The install went perfectly this time. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: after update - not all jpeg files are displayable
> Date: Tue, 28 Jul 2009 20:05:14 +0300 > From: Andriy Gapon > Sender: owner-freebsd-gn...@freebsd.org > > on 28/07/2009 19:56 Joe Marcus Clarke said the following: > > > > No. It's an issue with an incomplete PORTREVISION bump on ports which > > depend on libjpeg. Really, you need to do a portupgrade -rf jpeg to fix > > this. What you must avoid is one port being linked to both jpeg.9 and > > .10. When that happens, applications crash trying to open JPEGs. > > This is not an issue for me as far I can see. > libchk reported that no binaries/libraries were linked to libjpeg.so.9 in > lib/compat/pkg - I have even removed it now from . > Everything is linked to libjpeg.so.10, no unresolved libraries. > > Any further suggestions? > Maybe you could try to reproduce the issue for yourself? I have had things slip through libchk in the past. I did a 'portupgrade -rf jpeg' and rebuilt about 295 ports on all three of my systems running Gnome. That seems to have gotten everything happy again. (Of course, rebuilding 290+ ports does take a bit of time.) Gee.This might be a good time to try 8.0-Beta! You will need to re-build all ports then, anyway. ;-) -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: after update - not all jpeg files are displayable
> Date: Tue, 28 Jul 2009 20:04:24 +0200 > From: Oliver Lehmann > > Kevin Oberman wrote: > > > I did a 'portupgrade -rf jpeg' and rebuilt about 295 ports on all three > > of my systems running Gnome. That seems to have gotten everything happy > > again. (Of course, rebuilding 290+ ports does take a bit of time.) > > By the way - is there a way to print out what ports would be rebuilt? I > definitly do not want to rebuild openoffice or jdk. I tried to specify > some ignore patterns on cmdline but they where somehow ignored and an > openoffice rebuild was triggered (which i interruped as soon as I > detected it). portupgrade -rnf jpeg To avoid rebuilding OOo and jdk, use '-x openoffice.org -x jdk'. I do this, myself, and rebuild OOo during off times. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [HEADUP] FreeBSD Gecko's TODO and plan for future
I just rebuilt all of the ports that depended on firefox and I found the following dependencies remained: galeon-2.0.7_1 gnome2-fifth-toe-2.26.3 gnome2-power-tools-2.26.3 mplayerplug-in-3.55_3 muine-0.8.10_1 serpentine-0.7_5 Of these, muine and mplayerplug-in are broken and can't be re-built and serpentine is inheriting the dependency from muine. The two metaports are clearly just inheriting it. I think galeon is the only port that really insists on using firefox. (I have not looked at the Makefile or anything else in the galeon port as I have not used galeon in years and will just delete it. mpalyerplug-in is not marked as broken, but I get the error: c++ -c -o plugin.o -Wall -DXP_UNIX -DMOZ_X11 -I/usr/local/include/firefox/java -I/usr/local/include/firefox/plugin -I/usr/local/include/nspr -I/usr/local/include/firefox -I/usr/local/include/firefox/xpcom -I/usr/local/include/firefox/string -I/usr/local/include/firefox -O2 -fno-strict-aliasing -pipe -D_THREAD_SAFE -I/usr/local/include -D_THREAD_SAFE -I/usr/local/include -I/usr/local/include -DBSD -O2 -fno-strict-aliasing -pipe -Iinclude -fPIC -D_THREAD_SAFE -I/usr/local/include/gtk-2.0 -I/usr/local/lib/gtk-2.0/include -I/usr/local/include/atk-1.0 -I/usr/local/include/cairo -I/usr/local/include/pango-1.0 -I/usr/local/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/pixman-1 -I/usr/local/include/freetype2 -D_THREAD_SAFE -I/usr/local/include/gtk-2.0 -I/usr/local/lib/gtk-2.0/include -I/usr/local/include/atk-1.0 -I/usr/local/include/cairo -I/usr/local/include/pango-1.0 -I/usr/local/include -I/usr/local/include/glib-2.0 -I/usr/l ocal/lib/glib-2.0/include -I/usr/local/include/pixman-1 -I/usr/local/include/freetype2 -D_REENTRANT -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -DGTK_ENABLED Source/plugin.cpp In file included from Source/nsScriptablePeer.h:48, from Source/plugin.h:54, from Source/plugin.cpp:37: Source/nsIScriptableMplayerPlugin.h:41:84: error: macro "NS_DEFINE_STATIC_IID_ACCESSOR" passed 2 arguments, but takes just 1 Source/nsIScriptableMplayerPlugin.h:254:92: error: macro "NS_DEFINE_STATIC_IID_ACCESSOR" passed 2 arguments, but takes just 1 In file included from Source/nsScriptablePeer.h:48, from Source/plugin.h:54, from Source/plugin.cpp:37: Source/nsIScriptableMplayerPlugin.h:25: error: function definition does not declare parameters Source/nsIScriptableMplayerPlugin.h:122: error: expected constructor, destructor, or type conversion before 'class' Joe, since you are the maintainer, have you any idea why this is blowing up when built against libxul? -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [HEADUP] FreeBSD Gecko's TODO and plan for future
> Date: Tue, 25 Aug 2009 10:23:59 +1000 > From: Andrew Reilly > Sender: owner-freebsd-gn...@freebsd.org > > On Sun, Aug 23, 2009 at 10:26:25PM -0400, Joe Marcus Clarke wrote: > > You can set WITH_GECKO=libxul in make.conf, and most of these should go > > away. > > I've done that (and installed libxul!) and re-built all of the > ports in firefox-2.*/+REQUIRED_BY, and my list is now: > > alacarte-0.12.1_1 > brasero-2.26.3_1 > cairo-clock-0.3.2_3 > cheese-2.26.3_1 > deskbar-applet-2.26.2_1 > empathy-2.26.2_1 > eog-2.26.3_1 > epiphany-2.26.3_3 > epiphany-extensions-2.26.1_1 > gnome-control-center-2.26.0_2 > gimp-2.6.6,2 > gnome-applets-2.26.3_1 > gnome-games-2.26.3_1 > gnome2-2.26.3 > gtkam-gnome-0.1.16.1_1 > hamster-applet-2.26.3_1 > orca-2.26.3_1 > seahorse-plugins-2.26.2_2 > sound-juicer-2.26.1_1 > > > That's a lot shorter than it was before, but still clearly quite > long. In most of these I can't see where the firefox dependency > is coming from. For instance, the gimp meta-port is still here, > but gimp-app has moved over to the libxul-1.9 +REQUIRED_BY list. > > Is there any convenient way to list dependencies hierarchially, > rather than the flat set that pkg_info -r provides? Andrew, How did you sequence the re-builds? I'd guess that gimp-app was re-built after the gimp metaport, so the metaport retained the dependency. If you have portupgrade, I would suggest 'portupgrade -rfx firefox firefox'. portupgrade works by building a dependency graph of the needed ports and builds te tree from the root. This should get rid of all but a handful of ports. It looks like everything in the list should rebuild without the firefox dependency. I had every one of them. I'm now down to just mplayerplug-in because it fails to build against libxul. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [HEADUP] FreeBSD Gecko's TODO and plan for future
> Date: Tue, 25 Aug 2009 12:11:35 +1000 > From: Andrew Reilly > > On Mon, Aug 24, 2009 at 06:18:47PM -0700, Kevin Oberman wrote: > > > Date: Tue, 25 Aug 2009 10:23:59 +1000 > > > From: Andrew Reilly > > > Is there any convenient way to list dependencies hierarchially, > > > rather than the flat set that pkg_info -r provides? > > > > How did you sequence the re-builds? I'd guess that gimp-app was re-built > > after the gimp metaport, so the metaport retained the dependency. > > More or less: > for i in $(pkg_info -q -o $(cat /var/db/pkg/firefox-2.0.0.20_9,1/+REQUIRED_BY > )); do >echo $i: >cd /usr/ports/$i >sudo make build deinstall reinstall clean > done > > > If you have portupgrade, I would suggest 'portupgrade -rfx firefox > > firefox'. portupgrade works by building a dependency graph of the needed > > ports and builds te tree from the root. This should get rid of all but a > > handful of ports. > > I've stopped using portupgrade in favour of portmaster, but I > don't see a ready equivalent to this with portmaster, hence my > dumb script. In particular, I don't think that portmaster can > combine the -r and -x flags (depend and exclude), and when I've > done -f -r in combination before, then it seems to build the > entire transitive closure of dependencies, rather than just the > immediate ones. Sadly, there is no good way I know of to avoid this. > Hence my question about a tool to manipulate the dependency > graph as a graph... That I can help with. It does mean using portupgrade, but not to actually upgrade anything. 'portupgrade -nrfx firefox firefox' will provide a trivially parsable list. If the list is short, cut & paste can do it quickly. It's possible that portmaster has a similar capability. > Maybe the list will get shorter if I just repeat the rebuild > process a few times?... It will, but using the order from the command above will save time. > > It looks like everything in the list should rebuild without the firefox > > dependency. I had every one of them. I'm now down to just > > mplayerplug-in because it fails to build against libxul. > > That's good to know. It'd be nice to be able to get rid of > firefox2, if it's not going to get security patches. Yes, as soon as I can build mplayerplug-in without it, it's history. And none too soon. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
serpentine port forces dependency on muine
I have been trying to remove all dependencies on the broken muine port
and discovered that an error in the serpentine port Makefile causes
serpentine to always depend on muine.
The Makefile uses the config option MUINE to indicate whether to build
the muine plugin, but the script then checks "WITH_MUINE" and always
build the muine plugin and creates a dependency on muine.
I have opened PR ports/138179.
I patched the Makefile with:
--- sysutils/serpentine/Makefile.orig 2009-08-25 10:45:24.0 -0700
+++ sysutils/serpentine/Makefile2009-08-25 10:07:00.0 -0700
@@ -29,7 +29,7 @@
.include
-.if (defined(WITH_MUINE) || exists(${LOCALBASE}/bin/muine)) && ${ARCH}=="i386"
+.if (defined(MUINE) || exists(${LOCALBASE}/bin/muine)) && ${ARCH}=="i386"
BUILD_DEPENDS+=muine:${PORTSDIR}/audio/muine
RUN_DEPENDS+= muine:${PORTSDIR}/audio/muine
PLIST_SUB+=MUINE=""
This may not be the best way as it overloads the MUINE variable
differently than it is now overloaded, but it looks like it is logically
correct.
The obvious alternative is to add:
.if defined(MUINE)
WITH_MUINE= yes
.endif
--
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: ober...@es.net Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: serpentine port forces dependency on muine
> Date: Wed, 26 Aug 2009 01:50:01 +0300
> From: Peter Pentchev
>
> On Tue, Aug 25, 2009 at 11:06:18AM -0700, Kevin Oberman wrote:
> > I have been trying to remove all dependencies on the broken muine port
> > and discovered that an error in the serpentine port Makefile causes
> > serpentine to always depend on muine.
> >
> > The Makefile uses the config option MUINE to indicate whether to build
> > the muine plugin, but the script then checks "WITH_MUINE" and always
> > build the muine plugin and creates a dependency on muine.
> >
> > I have opened PR ports/138179.
> >
> > I patched the Makefile with:
> > --- sysutils/serpentine/Makefile.orig 2009-08-25 10:45:24.0
> > -0700
> > +++ sysutils/serpentine/Makefile2009-08-25 10:07:00.0 -0700
> > @@ -29,7 +29,7 @@
> >
> > .include
> >
> > -.if (defined(WITH_MUINE) || exists(${LOCALBASE}/bin/muine)) &&
> > ${ARCH}=="i386"
> > +.if (defined(MUINE) || exists(${LOCALBASE}/bin/muine)) && ${ARCH}=="i386"
> > BUILD_DEPENDS+=muine:${PORTSDIR}/audio/muine
> > RUN_DEPENDS+= muine:${PORTSDIR}/audio/muine
> > PLIST_SUB+=MUINE=""
>
> E...
>
> I strongly doubt that this is the reason for your problems.
>
> Actually, this is exactly how the Ports Collection's "options" framework
> is supposed to work: the OPTIONS variable lists just the names of
> the options, then bsd.port.mk prompts the user through a dialog
> (or just uses the options' default values) and sets either WITH_name
> or WITHOUT_name. The port then checks for WITH_name or WITHOUT_name,
> just as it does in this case. The option is named "MUINE", but
> the bsd.port.mk framework will set "WITH_MUINE" if the user wants it,
> or WITHOUT_MUINE if she doesn't (or building in batch mode, since
> the option defaults to Off).
>
> So the Makefile check is actually correct.
>
> I find it a little bit hard to believe that it is exactly this change
> to the Makefile that helped you get a serpentine build without muine.
> Could it be that, in the meantime, you had also removed the muine
> port itself? The Makefile check will be satisfied if the MUINE option
> is enabled *or* if the "muine" executable is present in /usr/local/bin.
> This is most probably because the serpentine configure script looks for
> muine itself and uses it unconditionally if it finds it.
>
> So... maybe you just had a /usr/local/bin/muine, and that made
> the serpentine port always build with it? Because the Makefile check
> is actually correct as per the ports options framework :/
Ack. You are correct.
If muine found in /usr/local/bin/, it will be built with the plug-in,
regardless of which way the MUINE configure option is set because:
.if (defined(MUINE) || exists(${LOCALBASE}/bin/muine)) && ${ARCH}=="i386"
As a result, you can't deinstall muine as serpentine depends on it, but
you can't build serpentine without a dependency on muine until you
deinstall muine. I am confused as to the whole point of this structure.
If muine is installed, serpentine will be built with the plugin...end of
story. The configuration option does nothing. The only effect it has is
to force the installation of muine on the initial install muine is not
already installed.
I guess the right way is to change the statement to read:
.if defined(MUINE) && ${ARCH}=="i386"
Or, since muine looks to be dead, just rip out the muine stuff.
--
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: ober...@es.net Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: serpentine port forces dependency on muine
> Date: Wed, 26 Aug 2009 07:05:12 +0100
> From: Matthew Seaman
>
> Kevin Oberman wrote:
>
> > If muine found in /usr/local/bin/, it will be built with the plug-in,
> > regardless of which way the MUINE configure option is set because:
> > .if (defined(MUINE) || exists(${LOCALBASE}/bin/muine)) && ${ARCH}=="i386"
>
> This is incorrect behaviour in any case: ports should not arbitrarily change
> configuration depending on what is or is not already installed, and user
> choices from OPTIONS dialogues should be paramount. The test should be:
>
> .if defined(WITH_MUINE) && !defined(WITHOUT_MUINE) && ${ARCH} =="i386"
The more I look at this port, the stranger it is. It has OPTIONS=, but
does not include bsd.port.options.mk. It then uses tests on a variable
named MUINE (same as the option), not WITH_MUINE or WITHOUT_MUINE.
This effectively makes the "option" not an option, at all. Serpentine
is ALWAYS built with the muine plug-in and, since the muine port is
broken (probably forever), this effectively breaks serpentine.
I am baffled as to how this came to pass. The maintainer (ahze) knows a
lot more about FreeBSD porting than I do, so I have to believe that
there is some sense behind this, but I don't see it.
As serpentine is a part of the gnome2-power-tools metaport and a LOT of
folks are likely to be re-building a lot of ports due to the V8.0
release, I'd really like to see it fixed.
This does not effect me any longer as I have commented out the part of
the configuration that enables the muine plug-in, rebuilt serpentine,
and deinstalled muine, but I am sure it will cause problems for others.
--
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: ober...@es.net Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: serpentine port forces dependency on muine
> Date: Thu, 27 Aug 2009 02:10:06 +0300
> From: Peter Pentchev
>
> On Wed, Aug 26, 2009 at 11:47:48AM -0700, Kevin Oberman wrote:
> > > Date: Wed, 26 Aug 2009 07:05:12 +0100
> > > From: Matthew Seaman
> > >
> > > Kevin Oberman wrote:
> > >
> > > > If muine found in /usr/local/bin/, it will be built with the plug-in,
> > > > regardless of which way the MUINE configure option is set because:
> > > > .if (defined(MUINE) || exists(${LOCALBASE}/bin/muine)) &&
> > > > ${ARCH}=="i386"
> > >
> > > This is incorrect behaviour in any case: ports should not arbitrarily
> > > change configuration depending on what is or is not already installed,
> > > and user
> > > choices from OPTIONS dialogues should be paramount. The test should be:
> > >
> > > .if defined(WITH_MUINE) && !defined(WITHOUT_MUINE) && ${ARCH} =="i386"
> >
> >
> > The more I look at this port, the stranger it is.
>
> Uhm, no it isn't, not really :)
>
> > It has OPTIONS=, but does not include bsd.port.options.mk.
>
> It includes bsd.port.pre.mk before testing the option. The part that
> takes care of displaying the dialog window to the user is in
> bsd.port.pre.mk. This part of the port's Makefile is correct.
Whole this may work, it is not recommended by the Porter's
Handbook. (See 5.11.2.2). Still, I suspect it does work as used here.
>
> > It then uses tests on a variable named MUINE (same as the option),
> > not WITH_MUINE or WITHOUT_MUINE.
>
> No it doesn't. The port's Makefile uses tests on WITH_MUINE (line 32).
> It then adds a variable named MUINE to the PLIST_SUB - the variable
> that contains the substitutions to be made in the pkg-plist file.
> And indeed, the pkg-plist file contains a couple of lines with
> %%MUINE%% in them - that part works, too, because the port adds
> MUINE to PLIST_SUB. This part of the port's Makefile is also correct.
Yes, I was wrong about this.
> > This effectively makes the "option" not an option, at all. Serpentine
> > is ALWAYS built with the muine plug-in and, since the muine port is
> > broken (probably forever), this effectively breaks serpentine.
>
> No it isn't. Serpentine is always built with muine *only* if the muine
> port is installed on the system at the time serpentine is build, as
> I explained in the previous message.
>
> Witness - on my system, where I *don't* have muine installed:
Yes, this right, too.
> There is some sense. As I explained in my previous mail, this will
> work just fine if the muine port is not installed on the system at
> the time serpentine is built. This is true for the package building
> cluster, and it is true for some of us who build our ports this way.
>
> Now... I do agree that having a port change its behavior depending
> on what is installed on the system is not really a good idea. It used
> to be considered a good idea - I remember a time when many, many ports
> did this instead of making the user define lots of variables when
> the options framework did not exist yet :) The idea was to make it *easy*
> for the user - if she has installed muine, then she most probably *wants*
> other apps to support muine, so the serpentine port just goes ahead and
> does the right thing without asking. Probably the WITH_MUINE knob was
> present even then, before the options framework - and many people
> considered this actually comfortable - "Yes, I know I can define this
> variable to make serpentine build with muine support, but I don't even
> have to do this - I just build muine beforehand and it's all right".
>
> Even then, I was one of the people who didn't like this, and I removed
> such autodetection in all the ports I took over, years ago. Still,
> other maintainers felt that this was useful and comfortable for the users.
>
> This behavior should have been removed when the OPTIONS variable was
> added to the port - now there *is* an easy way for the user to specify
> whether she wants muine or not. This part I agree with, and I think
> that it should be removed now.
>
> I'm just writing all of this to try to explain the point of view that
> led to this situation in the first place, in revision 1.2 of the
> Makefile, four years ago. At that time, the options framework was
> not completely finished yet, and users still had to specify WITH_*
> and WITHOUT_* variables manually, either on the command line or in
> elaborate config files; thus, the autodetection of muine was, indeed,
> considered by some to be a useful thing. Now, I think
Re: [Call for Testing] X.org 7.5 for FreeBSD
> Date: Fri, 19 Mar 2010 18:15:05 +0100 > From: Torfinn Ingolfsen > Sender: owner-freebsd-...@freebsd.org > > On Fri, Mar 19, 2010 at 11:03 AM, Gary Jennejohn > wrote: > > > > > First a question: why does 'make deinstall' give this output: > ===> Deinstalling dbus-1.2.16_1 > pkg_delete: unable to completely remove directory > '/usr/local/include/dbus-1.0/dbus' > pkg_delete: unable to completely remove directory > '/usr/local/include/dbus-1.0' > pkg_delete: unable to completely remove directory > '/usr/local/etc/dbus-1/system.d' > pkg_delete: unable to completely remove directory '/usr/local/etc/dbus-1' > pkg_delete: couldn't entirely delete package (perhaps the packing list is > incorrectly specified?) > > And what are these files: > r...@kg-v7# ls /usr/local/etc/dbus-1/s* > ConsoleKit.conforg.freedesktop.PolicyKit.conf > org.freedesktop.PolicyKit1.conf.dist > hal.conforg.freedesktop.PolicyKit1.conf > org.gnome.GConf.Defaults.conf For most ports, de-installation does not remove configuration files so that an upgrade does not require re-configuration. If configuration files exist, the removal of the directories created by the installation will fail. This is normal, but the message is disturbing. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: HEADS UP: ports/ and 10.0-CURRENT
On Mon, Sep 26, 2011 at 9:03 PM, Ade Lovett wrote: > With the advent of the conversion of HEAD to 10.0-CURRENT and, as to be > expected, ports/ is going to be essentially unusable for a while. > > The issue stems from configure scripts (to choose something completely > at random) assuming that FreeBSD would never jump to a double-digit > major version number, and as such, various regexps for "freebsd1*" (ie: > FreeBSD 1.1.x) are now matching "freebsd10". > > This is going to be some fairly fundamental breakage. > > However, until such time as 9.0-RELEASE is completely out of the door, > with autotools hat on, I will _not_ be committing any changes to > infrastructural ports to "fix" this. > > That is to say, until 9.0-R happens, and for some considerable period > afterwards, ya'll can pretty much expect ports/ to be non-functional on > HEAD. PRs mentioning this will be gleefully closed referencing this > message. aDe, Could an entry to this effect be added to UPDATING (with a matching entry when ports/ is "unbroken"). Anyone running CURRENT should be reading your message, but I'm a "belt and suspenders" type of guy on this sort of thing. Backing out of CURRENT and moving to 9-STABLE can be a REAL pain that will likely rapidly get worse as HEAD gets less and less frozen. -- R. Kevin Oberman, Network Engineer - Retired E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: HEADS UP: ports/ and 10.0-CURRENT
On Mon, Sep 26, 2011 at 10:01 PM, Garrett Cooper wrote: > It's not the FreeBSD dev's fault. Unfortunately the autotools folks > were microoptimizing and didn't consider that the future would come > sooner than it actually did. Garrett, First, I'm not complaining or criticizing any of the developers and I am very grateful to aDe for maintaining them as I get a headache every time I start looking at them. I am baffled in my attempts to parse "didn't consider that the future would come sooner than it actually did". Is that what you really meant, because it's self-contradictory? Or am I just confused. -- R. Kevin Oberman, Network Engineer - Retired E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: audio/cdparanoia broken on -CURRENT, and probably on 9.0
> On Fri, Oct 07, 2011 at 03:46:22 -0400, b. f. wrote: > > Just a note to say that recent changes on -CURRENT (r225950, meaning > > that it is probably broken on 9.0 after r226067) have broken > > audio/cdparanoia, and it should be fixed or marked as BROKEN there. I > > haven't filed a PR, or attempted to patch it yet -- I think that it > > would be worthwhile to look into moving to 10.2, which has a large > > number of improvements, although suffering from some Linuxisms. > > This will be easy to patch, using one of two methods: > > - change struct scsi_sense_data to struct scsi_sense_data_fixed > or, better yet: > - use scsi_extract_sense_len(), which will work for fixed or descriptor > sense. Ken, OK. I have grepped through all of the cdparanoia sources and fine no instances of scsi_sense_data. Where in the heck do I find it so I can get this port built? 10.2 would be lovely, but I just need cdparanoia on 9-stable quickly and I fear that hte package will no longer work after r226067. Sorry for breaking the thread, but I am not subscribed to ports. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: audio/cdparanoia broken on -CURRENT, and probably on 9.0
On Tue, Oct 11, 2011 at 8:33 PM, Kenneth D. Merry wrote: > On Tue, Oct 11, 2011 at 15:52:35 -0700, Kevin Oberman wrote: >> > On Fri, Oct 07, 2011 at 03:46:22 -0400, b. f. wrote: >> > > Just a note to say that recent changes on -CURRENT (r225950, meaning >> > > that it is probably broken on 9.0 after r226067) have broken >> > > audio/cdparanoia, and it should be fixed or marked as BROKEN there. I >> > > haven't filed a PR, or attempted to patch it yet -- I think that it >> > > would be worthwhile to look into moving to 10.2, which has a large >> > > number of improvements, although suffering from some Linuxisms. >> > >> > This will be easy to patch, using one of two methods: >> > >> > - change struct scsi_sense_data to struct scsi_sense_data_fixed >> > or, better yet: >> > - use scsi_extract_sense_len(), which will work for fixed or descriptor >> > sense. >> >> Ken, >> >> OK. I have grepped through all of the cdparanoia sources and fine no >> instances of scsi_sense_data. Where in the heck do I find it so I can >> get this port built? 10.2 would be lovely, but I just need cdparanoia >> on 9-stable quickly and I fear that hte package will no longer work >> after r226067. > > There is no FreeBSD support in cdparanoia by default. It is patched in by > the ports system. > > Go into the directory for the port, do a 'make fetch' and then 'make patch'. > > Then go into cdparanoia-III-alpha9.8/interface and copy the attached file > on top of scsi_interface.c. > > I've checked that it compiles on a system running code before the change, > but I think that change should work for systems before or after the change. > > Let me know whether it works for you. Thanks so much! Yes, the new scsi_interface.c compiled cleanly and cdparanoia built and installed. I am in the process of re-building all ports after I upgraded my system to 9-stable, so I really can't plug in my CD and try ripping aomething right now, but I'll try soonand let you know how it worked. Thanks again! -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: audio/cdparanoia broken on -CURRENT, and probably on 9.0
On Tue, Oct 11, 2011 at 9:00 PM, Kevin Oberman wrote: > On Tue, Oct 11, 2011 at 8:33 PM, Kenneth D. Merry wrote: >> On Tue, Oct 11, 2011 at 15:52:35 -0700, Kevin Oberman wrote: >>> > On Fri, Oct 07, 2011 at 03:46:22 -0400, b. f. wrote: >>> > > Just a note to say that recent changes on -CURRENT (r225950, meaning >>> > > that it is probably broken on 9.0 after r226067) have broken >>> > > audio/cdparanoia, and it should be fixed or marked as BROKEN there. I >>> > > haven't filed a PR, or attempted to patch it yet -- I think that it >>> > > would be worthwhile to look into moving to 10.2, which has a large >>> > > number of improvements, although suffering from some Linuxisms. >>> > >>> > This will be easy to patch, using one of two methods: >>> > >>> > - change struct scsi_sense_data to struct scsi_sense_data_fixed >>> > or, better yet: >>> > - use scsi_extract_sense_len(), which will work for fixed or descriptor >>> > sense. >>> >>> Ken, >>> >>> OK. I have grepped through all of the cdparanoia sources and fine no >>> instances of scsi_sense_data. Where in the heck do I find it so I can >>> get this port built? 10.2 would be lovely, but I just need cdparanoia >>> on 9-stable quickly and I fear that hte package will no longer work >>> after r226067. >> >> There is no FreeBSD support in cdparanoia by default. It is patched in by >> the ports system. >> >> Go into the directory for the port, do a 'make fetch' and then 'make patch'. >> >> Then go into cdparanoia-III-alpha9.8/interface and copy the attached file >> on top of scsi_interface.c. >> >> I've checked that it compiles on a system running code before the change, >> but I think that change should work for systems before or after the change. >> >> Let me know whether it works for you. > > Thanks so much! > > Yes, the new scsi_interface.c compiled cleanly and cdparanoia built > and installed. > > I am in the process of re-building all ports after I upgraded my > system to 9-stable, so I really can't plug in my CD and try ripping > aomething right now, but I'll try soonand let you know how it worked. Finally got all of my ports installed and re-booted with the DVD installed. Sorry to have taken so long, but rebuilding over 1600 ports on an old, slow laptop takes a lot of time and I had to tweak several port to get them to build. With the modified scsi_interface.c file you sent, cdparanoia seems to be working just fine. Thanks! Should I submit a PR with the new file? -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Unable to build swt-devel on systems with webkit-gtk2 installed
Looking back in the archive I see several messages about problems building x11-toolkits/swt-devel on systems with webkit-gtk2 installed. All fail with: [exec] cc -shared -s -o libswt-awt-gtk-3659.so swt_awt.o -L/usr/local/diablo-jdk1.6.0/jre/lib/i386 -ljawt [exec] make: don't know how to make make_webkit. Stop Is there any hope of getting this fixed? I'm totally out of my depth to try to figure out what needs to be done. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Strange issues while upgrading ports
ries, header files, data files, or anything else. It's the 11 step process and please read the relevant example in its entirety to make sure you don't waste too much time. If your system has a very large number of ports installed, consider using the -P option to use packages when they are available. I do see some ports that might benefit from CPU specific optimizations. If you feel that these are important, re-install these after you finish the basic re-installation. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Port: multimedia/handbrake
On Tue, Nov 29, 2011 at 4:43 AM, Chris Rees wrote: > On 29 November 2011 11:21, wrote: >> Hi, >> >> the version of HandBrake in the ports is outdated and can not be build under >> amd64. >> >> With the patches from http://www.bpsw.biz/handbrake-freebsd/ it is possible >> to build the current version (0.9.5) on amd64 (8.1 and 8.2 tested). I assume >> that this also works on i386, but did not test it. >> >> Can the Patches be integrated into the port please? >> >> Direct URL: http://www.bpsw.biz/handbrake-freebsd/download/handbrake- >> freebsd-0.9.5.tgz >> >> Disclosure: I did not write them. > > I'll have a look later today, if no-one beats me to it. > > For future reference, patches sometimes get 'lost' in this mailing > list, better to send a PR. > > http://www.freebsd.org/send-pr.html I have been working on getting Handbrake 0.9.5 to build on FreeBSD for some time. I had resolved a number of issues, but had no luck with some assembler issues in the ffmpeg portion. I am working on converting this work to a FreeBSD port Looks straight-forward, but no promises. I'll report on success (or failure) and submit a PR to get the port updated it that appears to be appropriate. I have maintained several ports over the years and still maintain one, so I have some experience with porting, but will hardly claim to be an expert. I suspect you have more expertise than I do, Chris, so feel free to take it over. Thanks for getting this out so others can use it! -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: dvdrip hang when PERL_VERSION=5.12.4
On Sat, Dec 10, 2011 at 10:33 AM, Gary Jennejohn wrote: > > I just noticed that dvdrip does not work when PERL_VERSION=5.12.4. > > Ths symptom is a hang as soon as the user tries to create a new project. > Here's the ps output: > 150 5360 4704 1 40 0 236740 47116 umtxn I 2 0:00.88 > /usr/local/bin/perl /usr/local/bin/dvdrip > > Note the umtxn. > > Forcing PERL_VERSION=5.8.9 and reinstalling dvdrip results in a working > copy and creating a new project returns basically immediately and everything > else also works. > > Just thought I'd report it for the archive. Ouch! umtxn is waiting on a kernel lock. This should NOT happen and it looks more like a kernel issue than a userland one. If you can still run dvdrip with 5.12.4, what does 'procstat -k PID" show? It should provide some useful kernel stack information. Also, what version of FreeBSD and is it on i386, and64, or some other? -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: lang/gcc46
On Mon, Dec 12, 2011 at 9:36 AM, Jason Hellenthal wrote: > > Hi Gerald, > > As a request once again similiar to one I have made in the past... Would it > be possible yet to slow down the update process for the gcc46 port ? > > This is turning out to be quite the pain in the U-Know-What with version > flapping and rebuilding because a port depends on it. If I am correct it is > updated weekly. I caught the tail end of the previous update and the day > after it was bumped to the next snapshot version & by the time both of those > were finished the port had once again been bumped to _1. > > Is there anything that could be done to stabalize this ... ? > > At this point I am left for the manual intervention of using +IGNOREME files > or excluding by whatever means neccesary as weekly updates seem completely > unneccesary now that alot of ports are shifting to depend on gcc46. > > Can a gcc46-devel port be branched for those that absolutely need the weekly > updates ? +1 gcc46 is used by so many ports that I am continually re-building it and on slow machines, this takes a while. How about a gcc46-devel port that gets the regular updates and let gcc46 stay stable when there are not major fixes? - R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: lang/gcc46
On Mon, Dec 12, 2011 at 10:11 AM, Sunpoet Po-Chuan Hsieh wrote: > On Mon, Dec 12, 2011 at 10:03:14AM -0800, Kevin Oberman wrote: >> On Mon, Dec 12, 2011 at 9:36 AM, Jason Hellenthal wrote: >> > >> > Hi Gerald, >> > >> > As a request once again similiar to one I have made in the past... Would >> > it be possible yet to slow down the update process for the gcc46 port ? >> > >> > This is turning out to be quite the pain in the U-Know-What with version >> > flapping and rebuilding because a port depends on it. If I am correct it >> > is updated weekly. I caught the tail end of the previous update and the >> > day after it was bumped to the next snapshot version & by the time both of >> > those were finished the port had once again been bumped to _1. >> > >> > Is there anything that could be done to stabalize this ... ? >> > >> > At this point I am left for the manual intervention of using +IGNOREME >> > files or excluding by whatever means neccesary as weekly updates seem >> > completely unneccesary now that alot of ports are shifting to depend on >> > gcc46. >> > >> > Can a gcc46-devel port be branched for those that absolutely need the >> > weekly updates ? >> +1 >> >> gcc46 is used by so many ports that I am continually re-building it >> and on slow machines, this takes a while. How about a gcc46-devel port >> that gets the regular updates and let gcc46 stay stable when there are >> not major fixes? > > We have lang/gcc already. This port is created for perferred gcc releases > (4.6.2 currently). What we're waiting for is a bsd.gcc.mk update to allow > users build ports with lang/gcc instead of lang/gcc46. Ahh. I see the issue. I have not looked at bsd.gcc.mk, but it does not seem like this should be too difficult. Just a matter of the right person having the time. Would ports specifying gcc46 need to be touched? -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: lang/gcc46
On Tue, Dec 13, 2011 at 8:30 AM, Jason Hellenthal wrote: > > > On Tue, Dec 13, 2011 at 06:05:40PM +0800, Gerald Pfeifer wrote: >> On Tue, 13 Dec 2011, Sunpoet Po-Chuan Hsieh wrote: >> > We have lang/gcc already. This port is created for perferred gcc >> > releases (4.6.2 currently). What we're waiting for is a bsd.gcc.mk >> > update to allow users build ports with lang/gcc instead of lang/gcc46. >> >> Actually, it's even better. :-) Replace lang/gcc46 by lang/gcc on >> your local systems, Kevin and Jason, and that (not lang/gcc46) will >> be used henceforth. >> >> There is a small issue in that this will not be recorded properly as >> a dependency when you build packages, but apart from that (if you use >> ports or ensure the lang/gcc package is present wherever you install >> things built that way, you should be good. >> >> Gerald > > Thanks Gerald and everyone else. Much appreciated. > > -- > ;s =; Yes, thanks! % portmaster -o lang/gcc lang/gcc46 seems to have worked just fine! -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkg_version and portversion: ports version comparison weirdness
On Sun, Dec 18, 2011 at 8:43 AM, Conrad J. Sabatier wrote: > Can anyone explain why I'm seeing the following? > > libX11-1.4.99.1 < needs updating (index has > 1.4.4,1) > > How is it that version 1.4.99.1 compares as "less than" 1.4.4,1? > Since when is 99 < 4? > > Is it the PORTEPOCH in 1.4.4,1 that's throwing a monkey wrench into the > works? > > This makes no sense to me. What is the logic being applied here? > Yes. When epoch increments it starts the versioning all over. Largest epoch value ALWAYS is considered "newer" that any smaller epoch value, regardless of the rest of the version number. Epoch is normally used when a port needs to be rolled back to an older version due to a serious problem caused by the newer version. E.g. xcb-utils-3.6 broke a LOT of stuff, so the epoch was bumped to 1 and the version was set back to 3.6. Once a port has an epoch applied, it will never be removed. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Stop in /usr/ports/multimedia/x264
On Wed, Dec 21, 2011 at 5:49 AM, Leslie Jensen wrote: > > Will you Please look at this? > > > > cc -Wshadow -O3 -ffast-math -O2 -pipe -fno-strict-aliasing -Wall -I. -O2 > -pipe -fno-strict-aliasing -fPIC -I/usr/local/include -std=gnu99 > -I/usr/local/include -I/usr/local/include -fPIC -fomit-frame-pointer > -fno-tree-vectorize -c -o input/input.o input/input.c > In file included from x264.c:50: > /usr/local/include/libavformat/avformat.h:158: warning: 'AVMetadata' is > deprecated > x264.c: In function 'print_version_info': > x264.c:250: error: 'X264_CSP_Iall' undeclared (first use in this function) > x264.c:250: error: (Each undeclared identifier is reported only once > x264.c:250: error: for each function it appears in.) > gmake: *** [x264.o] Fel 1 > gmake: *** Inväntar oavslutade jobb... > *** Error code 1 > > Stop in /usr/ports/multimedia/x264. > *** Error code 1 > > Stop in /usr/ports/multimedia/x264. > > ===>>> make failed for multimedia/x264 > ===>>> Aborting update I get this error on only a single system. My other two built the x264 port without any problems. I see the following errors during the configure stage: ===> Configuring for x264-0.119.2113 [[: not found freebsd8.2: not found [[: not found [[: not found [[: not found [: git: not found On a system that works I get: ./configure: [[: not found ./configure: freebsd9.0: not found ./configure: [[: not found fatal: Not a git repository (or any parent up to mount parent ) Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). The "X264_CSP_Iall: unexpected operator" would likely point to the problem. (Just starting to look.) The config options are identical. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Stop in /usr/ports/multimedia/x264
On Wed, Dec 21, 2011 at 4:04 PM, Kevin Oberman wrote: > On Wed, Dec 21, 2011 at 5:49 AM, Leslie Jensen wrote: >> >> Will you Please look at this? >> >> >> >> cc -Wshadow -O3 -ffast-math -O2 -pipe -fno-strict-aliasing -Wall -I. -O2 >> -pipe -fno-strict-aliasing -fPIC -I/usr/local/include -std=gnu99 >> -I/usr/local/include -I/usr/local/include -fPIC -fomit-frame-pointer >> -fno-tree-vectorize -c -o input/input.o input/input.c >> In file included from x264.c:50: >> /usr/local/include/libavformat/avformat.h:158: warning: 'AVMetadata' is >> deprecated >> x264.c: In function 'print_version_info': >> x264.c:250: error: 'X264_CSP_Iall' undeclared (first use in this function) >> x264.c:250: error: (Each undeclared identifier is reported only once >> x264.c:250: error: for each function it appears in.) >> gmake: *** [x264.o] Fel 1 >> gmake: *** Inväntar oavslutade jobb... >> *** Error code 1 >> >> Stop in /usr/ports/multimedia/x264. >> *** Error code 1 >> >> Stop in /usr/ports/multimedia/x264. >> >> ===>>> make failed for multimedia/x264 >> ===>>> Aborting update > > I get this error on only a single system. My other two built the x264 > port without any problems. > > I see the following errors during the configure stage: > ===> Configuring for x264-0.119.2113 > [[: not found > freebsd8.2: not found > [[: not found > [[: not found > [[: not found > [: X264_CSP_Iall: unexpected operator > git: not found > > On a system that works I get: > ./configure: [[: not found > ./configure: freebsd9.0: not found > ./configure: [[: not found > fatal: Not a git repository (or any parent up to mount parent ) > Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). > > The "X264_CSP_Iall: unexpected operator" would likely point to the > problem. (Just starting to look.) > > The config options are identical. ARGH! Did a cut and paste instead of copy and paste which made the above nonsense. I've fixed it above. Sorry! -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ports count milestone according to FreshPorts
On Wed, Dec 21, 2011 at 7:07 AM, Ruslan Mahmatkhanov wrote: > Mark Linimon wrote on 21.12.2011 18:55: >> According to http://www.freshports.org/ we have crossed the 23,000 port >> barrier (currently 23,031). If I read this correctly the commit that >> put us over the top was the addition of devel/py-Products.CMFActionIcons. > ^ > Is there any prizes like cellular ops do when they got their 100 > mobile subscriber connected? :) > >> >> I appreciate all the hard work folks put into the Ports Collection. Now >> I'll go back to trying to make sure we have a way to build them all :-) >> >> mcl > > -- > Regards, > Ruslan > > Tinderboxing kills... the drives. Of course! The 23,000th port contributor gets free unlimited FreeBSD downloads for life! :-) -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Stop in /usr/ports/multimedia/x264
On Thu, Dec 22, 2011 at 3:03 AM, wrote: > Kevin Oberman wrote: > >> I see the following errors during the configure stage: >> ===> Configuring for x264-0.119.2113 >> [[: not found > > That sure looks as if the configure script needs to be run with bash. > > files/patch-configure does this: > > -#!/bin/bash > +#!/bin/sh > > which presumes that the script does not actually need bash extensions. > However, since it does seem to need those extensions, that part of the > patch should be > > -#!/bin/bash > +#!/usr/local/bin/bash > > and bash needs to be added as a build dependency. (Alternatively, the > configure script could be patched to not use the [[ bash builtin.) > > Maintainer already in Cc: list. OK, but why does it build correctly on all of my other systems? All have bash installed, but none use it to configure x264, so, while I suspect it does cause the errors OTHER then the "[: X264_CSP_Iall: unexpected operator" error. None of the others breaks the build. Off to try configuring with bash. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Stop in /usr/ports/multimedia/x264
On Thu, Dec 22, 2011 at 3:03 AM, wrote: > Kevin Oberman wrote: > >> I see the following errors during the configure stage: >> ===> Configuring for x264-0.119.2113 >> [[: not found > > That sure looks as if the configure script needs to be run with bash. > > files/patch-configure does this: > > -#!/bin/bash > +#!/bin/sh > > which presumes that the script does not actually need bash extensions. > However, since it does seem to need those extensions, that part of the > patch should be > > -#!/bin/bash > +#!/usr/local/bin/bash > > and bash needs to be added as a build dependency. (Alternatively, the > configure script could be patched to not use the [[ bash builtin.) > > Maintainer already in Cc: list. Hmm. I just noticed the mm@ removed patch-configure from the port as the upstream now uses sh. So there is a problem, but it is not with the port. Looks like the upstream switched to sh, but sis not remove all of the "bash"isms. I edited configure to change from sh to bash and that makes it configure and build correctly. Looks like the configure script needs a bit of love to work correctly with sh, though I still am baffled as to why if built on 2 systems and failed on one. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Stop in /usr/ports/multimedia/x264
On Thu, Dec 22, 2011 at 1:32 AM, Martin Matuska wrote: > Say, did you look at the port recently? :-) > > I have added bash as a build dependency and use it for the configure script. > > There are two ways I can solve this in general: > 1.) add bash as a build dependency and use it for configure (I have > chosen this for now, already committed) > 2.) patch configure and remove/replace constructs unsupported by /bin/sh > (e.g. "==" or [[ ]]) Thanks for the quick fix, but I am still baffled as to why it built correctly on two of my three systems where it's installed. All three complained about the '[[' type constructs, but only one spit out the "x264_CSP|all" error and al of the other completed the build. It is possible that the build was not quite right as a result of the errors, but why did only one fail completely? The only thing I can think of is that the failing system is the oldest, running 8.2 while the others were running 9.0-RC2 and 9.0-Beta3. Again, thanks again for the quick fix. I tend to prefer #2 if there is no real reason for bash, but almost all systems used for multimedia work already have bash installed, so it's not a big deal. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Stop in /usr/ports/multimedia/x264
On Thu, Dec 22, 2011 at 10:57 AM, Chris Rees wrote: > > On 22 Dec 2011 18:20, "Ruslan Mahmatkhanov" wrote: >> >> Chris Rees wrote on 22.12.2011 22:12: >> > On 22 Dec 2011 16:49, "Ruslan Mahmatkhanov" wrote: >> >> >> >> Kevin Oberman wrote on 22.12.2011 20:38: >> >>> The only thing I can think of is that the failing system is the >> >>> oldest, running 8.2 while the others were running 9.0-RC2 and >> >>> 9.0-Beta3. >> >> >> >> Yes, all is worked just fine (before the bash fix commit) there on >> >> 10.0-CURRENT i386. I saw that configure warnings too, but it still was >> >> built successfully. May be bash only needed on some older FreeBSD >> >> versions like 8.2, that didn't had all that improvements for /bin/sh, >> >> that were merged in 9 and 10, so maybe it is the reason why it builded >> >> fine on this systems w/o any additional fixes. >> >> >> > >> > True, since 9 sh supports == -- however I might label this compatibility >> > shims, rather than 'improvements'... >> > >> > Chris >> >> I'm talking about overall /bin/sh work, not only about compatibility >> with some `non-true' shells. I know many things was done and tests >> coverage is terrific. >> So may we imply dependency on shells/bash and specific configure patches >> only if OSVERSION < 90? >> > > Trouble is with these problems is that they can hide, and don't always > result in outright failure (i've experienced this with musicpd and Clamav). > > The scripts need a proper audit before being declared sh-safe. > > Chris Yes! Even with versions where it works, I get a number of errors reported during configure. So, while it built, I am not sure that it built "right". I may be lacking optimizations or picking up bugs. Either the script should be fixed to be fully compatible with sh or bash should be used. I don't mind if it is dependent on bash for pre-9.0, but, again, I doubt many systems running multimedia apps lack the bash port, already, so requiring bash is probably going to impact few and the impact is pretty minor! -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: x11-fm/thunar Build error
On Sun, Jan 8, 2012 at 3:30 AM, Leslie Jensen wrote: > > > checking for gmsgfmt... /usr/local/bin/msgfmt > checking for perl... /usr/bin/perl > checking for perl >= 5.8.1... 5.14.2 > checking for XML::Parser... configure: error: XML::Parser perl module is > required for intltool > ===> Script "configure" failed unexpectedly. > Please report the problem to x...@freebsd.org [maintainer] and attach the > "/usr/ports/x11-fm/thunar/**work/Thunar-1.3.0/config.log" including the > output > of the failure of your make command. Also, it might be a good idea to > provide > an overview of all packages installed on your system (e.g. an `ls > /var/db/pkg`). > *** Error code 1 > > Stop in /usr/ports/x11-fm/thunar. > *** Error code 1 > > Stop in /usr/ports/x11-fm/thunar. > > ===>>> make failed for x11-fm/thunar > ===>>> Aborting update > > Assuming p5-XML-Parser is installed, re-install it. While I don't understand why, several times I have gotten this error on various ports and simply re-installing the port seems to fix it. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: x11-fm/thunar Build error
On Sun, Jan 8, 2012 at 10:24 AM, Chris Rees wrote: > On 8 January 2012 17:47, Kevin Oberman wrote: > > On Sun, Jan 8, 2012 at 3:30 AM, Leslie Jensen wrote: > > > >> > >> > >> checking for gmsgfmt... /usr/local/bin/msgfmt > >> checking for perl... /usr/bin/perl > >> checking for perl >= 5.8.1... 5.14.2 > >> checking for XML::Parser... configure: error: XML::Parser perl module is > >> required for intltool > >> ===> Script "configure" failed unexpectedly. > >> Please report the problem to x...@freebsd.org [maintainer] and attach > the > >> "/usr/ports/x11-fm/thunar/**work/Thunar-1.3.0/config.log" including the > >> output > >> of the failure of your make command. Also, it might be a good idea to > >> provide > >> an overview of all packages installed on your system (e.g. an `ls > >> /var/db/pkg`). > >> *** Error code 1 > >> > >> Stop in /usr/ports/x11-fm/thunar. > >> *** Error code 1 > >> > >> Stop in /usr/ports/x11-fm/thunar. > >> > >> ===>>> make failed for x11-fm/thunar > >> ===>>> Aborting update > >> > >> Assuming p5-XML-Parser is installed, re-install it. While I don't > > understand why, several times I have gotten this error on various ports > and > > simply re-installing the port seems to fix it. > > Did you update your perl without reinstalling p5-\*? > Nope. I always either run the after-update script or reinstall ports dependent on perl and make sure that the version-specific directories are empty, depending on what /usr/ports/UPDATING says to do. I've hit the problem with p5-XML-Parse on several occasions, on various systems. I'll admit that it was easier to re-install then to try to track down what was actually failing. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: cannot build x11-wm/xfce4-wm after upgrade x11/xcb-util
On Tue, Jan 17, 2012 at 11:18 AM, Heino Tiedemann wrote: > Hi, > > > after I did that: > > , > | 20120116: > | AFFECTS: users of x11/xcb-util > | AUTHOR: ga...@freebsd.org > | > | x11/xcb-util was updated to 0.3.8 and was split in new modules. > | Dependencies were adjusted but main port symbols were moved to a single > | library, xcb-util.so. For this reason, all dependent ports must be > | recompiled.If you use portmaster, run: > | > | # portmaster -R -r xcb-util-0 > | > | Or for portupgrade: > | > | # portupgrade -r xcb-util-0\* > ` > > > I got that: > > > gmake[3]: Entering directory > `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3/settings-dialogs' > CC xfwm4_settings-xfwm4-settings.o > CCLD xfwm4-settings > CC xfwm4_tweaks_settings-tweaks-settings.o > CCLD xfwm4-tweaks-settings > CC xfwm4_workspace_settings-workspace-settings.o > CCLD xfwm4-workspace-settings > libtool: link: cannot find the library `/usr/local/lib/libxcb-aux.la' or > unhandled argument `/usr/local/lib/libxcb-aux.la' > gmake[3]: *** [xfwm4-workspace-settings] Error 1 > gmake[3]: Leaving directory > `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3/settings-dialogs' > gmake[2]: *** [all] Error 2 > gmake[2]: Leaving directory > `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3/settings-dialogs' > gmake[1]: *** [all-recursive] Error 1 > gmake[1]: Leaving directory `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3' > gmake: *** [all] Error 2 > *** Error code 1 > > Stop in /usr/ports/x11-wm/xfce4-wm. > *** Error code 1 > > Stop in /usr/ports/x11-wm/xfce4-wm. > > > > Any ideas? > > Install sysutils/bsdadminscripts and use pkg_libchk to find the missed dependency. I just tracked down that metacity had been missed causing several ports to fail, but your case may well be something different. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Upgrading libs with many dependent ports
I have just been cleaning up the mess caused by the upgrade of xcb-utils. On my systmes I have hundreds of ports that will be re-built by the methods listed in UPDATING, even though the vast majority of them are only dependent on other ports that are dependent on xcb-utils, but don't actually load any of the libraries in xcb-utils. It is a huge waste of time and CPU cycles. I think that I can see two ways of eliminating the rebuilding of ports that don't need it. One is rather manual but can be done now while the other wou;d be automatic, but would need to be written by someone who is far better at writing shell scripts than I. The manual method would be to install sysutils/bsdadminscripts and use a command like `pkg_libchk | grep -E "xcb-.+.so" | sort > tmpfile` to provide a list of ports that actually are linked to the libraries in question. This would be fed into portmaster to rebuild just these ports. (I guess I could use awk and uniq to remove repeats.) Should this become a preferred method of handling this problem? -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Upgrading libs with many dependent ports
On Tue, Jan 17, 2012 at 6:09 PM, Matthew D. Fuller wrote:
> On Tue, Jan 17, 2012 at 05:51:11PM -0800 I heard the voice of
> Kevin Oberman, and lo! it spake thus:
> >
> > The manual method would be to install sysutils/bsdadminscripts and
> > use a command like `pkg_libchk | grep -E "xcb-.+.so" | sort >
> > tmpfile` to provide a list of ports that actually are linked to the
> > libraries in question.
>
> FWIW, I some years ago wrote up a quick&dirty perl script to find
> missing or out of date libs. It pulls out and warns about missing
> libs, stuff in compat/pkg (held over after upgrade by
> portupgrade/portmaster), and stuff in the base /usr/lib/compat (handy
> when crossing major versions, and potentially other big upheavals).
> It's only about a k; I'll attach it.
>
> I pretty much wind up ldd'ing /usr/local/{bin/*,sbin/*,lib/*.so*} and
> running the results through the script. Usually something like `cd
> /usr/local/bin ; ldd * > /tmp/ldd.bin ; lddchk.pl < /tmp/ldd.bin`.
> That tells me the files; then I can use my brain or pkg_which to tell
> me which packages are involved. I'm happy with that level of
> automation, because I like keeping my brain firmly in the loop on such
> things, but it wouldn't be too hard to extend it to do its own walks
> over the filesystem, etc.
>
Take a look at pkg_chklib. It is quite optimized and runs multiple checks
in parallel so that
you can run it on 1100 ports in about 1.5 minutes. Here is a sample o this
output:
%pkg_libchk | grep -E "xcb-.+.so" | sort
gok-2.30.1,1: /usr/local/bin/create-branching-keyboard misses
libxcb-atom.so.1
gok-2.30.1,1: /usr/local/bin/create-branching-keyboard misses
libxcb-aux.so.0
gok-2.30.1,1: /usr/local/bin/create-branching-keyboard misses
libxcb-event.so.1
gok-2.30.1,1: /usr/local/bin/gok misses libxcb-atom.so.1
gok-2.30.1,1: /usr/local/bin/gok misses libxcb-aux.so.0
gok-2.30.1,1: /usr/local/bin/gok misses libxcb-event.so.1
nautilus-open-terminal-0.18_4:
/usr/local/lib/nautilus/extensions-2.0/libnautilus-open-terminal.so misses
libxcb-atom.so.1
nautilus-open-terminal-0.18_4:
/usr/local/lib/nautilus/extensions-2.0/libnautilus-open-terminal.so misses
libxcb-aux.so.0
nautilus-open-terminal-0.18_4:
/usr/local/lib/nautilus/extensions-2.0/libnautilus-open-terminal.so misses
libxcb-event.so.1
vlc-1.1.13,3: /usr/local/lib/vlc/plugins/control/libglobalhotkeys_plugin.so
misses libxcb-keysyms.so.1
vlc-1.1.13,3:
/usr/local/lib/vlc/plugins/video_output/libxcb_window_plugin.so misses
libxcb-keysyms.so.1
yelp-2.30.2_1: /usr/local/bin/yelp misses libxcb-atom.so.1
yelp-2.30.2_1: /usr/local/bin/yelp misses libxcb-aux.so.0
yelp-2.30.2_1: /usr/local/bin/yelp misses libxcb-event.so.1
%
And it is already in ports.
--
R. Kevin Oberman, Network Engineer
E-mail: kob6...@gmail.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Correcting problems disclosed by pkg_libchk
On Wed, Jan 18, 2012 at 5:02 AM, Carmel wrote: > On another thread I noticed a reference to "pkg_libchk". I was > interested in seeing what it would disclose on my system, so I ran it. > > pkg_libchk -Rrv > > It produced a great deal of output. This is one section dealing with > "Firefox" > > firefox-9.0.1,1: located: > /usr/local/lib/firefox/components/libbrowsercomps.so misses libmozalloc.so > found at /usr/local/lib/firefox/libmozalloc.so. > firefox-9.0.1,1: located: > /usr/local/lib/firefox/components/libdbusservice.so misses libmozalloc.so > found at /usr/local/lib/firefox/libmozalloc.so. > firefox-9.0.1,1: located: /usr/local/lib/firefox/components/libmozgnome.so > misses libmozalloc.so found at /usr/local/lib/firefox/libmozalloc.so. > firefox-9.0.1,1: located: /usr/local/lib/firefox/firefox-bin misses > libmozalloc.so found at /usr/local/lib/firefox/libmozalloc.so. > firefox-9.0.1,1: located: /usr/local/lib/firefox/libsoftokn3.so misses > libmozsqlite3.so found at /usr/local/lib/firefox/libmozsqlite3.so. > firefox-9.0.1,1: located: /usr/local/lib/firefox/libxpcom.so misses > libmozalloc.so found at /usr/local/lib/firefox/libmozalloc.so. > firefox-9.0.1,1: located: /usr/local/lib/firefox/libxul.so misses > libmozsqlite3.so found at /usr/local/lib/firefox/libmozsqlite3.so. > firefox-9.0.1,1: located: /usr/local/lib/firefox/libxul.so misses > libmozalloc.so found at /usr/local/lib/firefox/libmozalloc.so. > firefox-9.0.1,1: located: /usr/local/lib/firefox/plugin-container misses > libmozalloc.so found at /usr/local/lib/firefox/libmozalloc.so. > firefox-9.0.1,1: located: /usr/local/lib/firefox/sdk/lib/libxpcom.so > misses libmozalloc.so found at /usr/local/lib/firefox/libmozalloc.so. > firefox-9.0.1,1: located: /usr/local/lib/firefox/sdk/lib/libxul.so misses > libmozsqlite3.so found at /usr/local/lib/firefox/libmozsqlite3.so. > firefox-9.0.1,1: located: /usr/local/lib/firefox/sdk/lib/libxul.so misses > libmozalloc.so found at /usr/local/lib/firefox/libmozalloc.so. > > If I am reading this correctly, the libmozalloc.so library is missing. I > have tried doing a forced re-install of Firefox, but the same condition > exists. Other packages have several libraries apparently missing also. > Since re-installing the port does not seem to alleviate the problem, > what is the prescribed method of correcting it? > > Thanks! > No, it is telling you that the files listed seem to miss the libraries re[ported, but that they were found in /usr/local/lib/firefox. Firefox does its own thing for finding its sharable libs, so /usr/local/lib/firefox is not in the loader hint, but firefox knows where they are and does load them. this is a side effect of -v. You asked for false positives and you got them. Oh, and specifying -R or -r is only relevant when a specific port is listed. 'pkg_libchk -Rrv' does nothing more than just 'pkg_libchk -v'. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: xcb-util
On Wed, Jan 18, 2012 at 6:08 PM, Jason Hellenthal wrote: > > > On Wed, Jan 18, 2012 at 05:46:07PM -0600, ajtiM wrote: > > On Wednesday 18 January 2012 08:28:38 Volodymyr Kostyrko wrote: > > > Subbsd wrote: > > > > I found two broken rebuild after upgrade xcb: > > > > > > > pkg_libchk from sysutils/bsdadminscripts would point you to all ports > > > that should be rebuilt. > > > > I ran pkg_libchk and I got: > > diablo-jdk-16 misses libz.so.4 > > Unrelated to the issue... > > FYI the above package provides what the below package is utilized for. > > > diablo-jre-16 misses libz.so.4 > > and both misses liodbcinst.so > FYI The man page for pkg_libchk discusses this and explains that thy are false positives. pkg_libchk -o | grep xcb- should just give the relevant information. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: "portmaster -o" behaves a little strangely (IMHO)
On Tue, Jan 24, 2012 at 7:14 AM, Conrad J. Sabatier wrote: > On Tue, 24 Jan 2012 09:21:05 -0500 > Michael Scheidell wrote: >> >> On 1/24/12 9:19 AM, Conrad J. Sabatier wrote: >> > # portmaster -CK -o lang/gcc46 gcc-4.4.7.2008 >> > >> what happens with: >> >> # portmaster -CK -o lang/gcc46 lang/gcc44 >> >> ? > > Well, since gcc44 is no longer installed, I just tried: > > portmaster -o lang/gcc47 lang/gcc46 > > And the actions that started were much more along the lines of what I > was expecting. The build of gcc47 is currently underway as I write > this. > > So, it seems it's not a good idea to "mix and match" port origins with > port names in the case of this particular option. Could this be > considered a "bug"? It certainly seems to at least qualify as a > "quirk", I would say. :-) > > -- > Conrad J. Sabatier > conr...@cox.net I wanted to note is that you installed lang/gcc46, the development version of the compiler. It gets updated very frequently and you may want this, but it is probably better for most people to install lang/gcc which is the stable version of gcc-4.6. It gets updated only when a new gcc-4.6 version is released, so it does not get updated nearly so often. Posts that depend on USE_FORTRAN or USE_GCC=4.6+ will both be happy with lang/gcc, though they will pull in the development version if no gcc-4.6 is installed. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: cannot build x11-wm/xfce4-wm after upgrade x11/xcb-util
On Thu, Jan 26, 2012 at 5:23 AM, Torfinn Ingolfsen wrote: > Hello, > > On Thu, Jan 26, 2012 at 1:24 AM, Zhihao Yuan wrote: > >> On Tue, Jan 17, 2012 at 10:39 PM, Heino Tiedemann >> wrote: >> > Michael Johnson wrote: >> > >> >> Out of curiosity, what does 'grep xcb-aux >> /usr/local/libdata/pkgconfig/*' >> >> show? >> > >> > Nothing. No Output. >> > >> > Heino >> > >> > ___ >> > freebsd-ports@freebsd.org mailing list >> > http://lists.freebsd.org/mailman/listinfo/freebsd-ports >> > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" >> >> I solved this problem by rebuilding libxfce4menu (to update the >> libtool profile). >> >> I tried that, but it didn't help here. I used 'portupgrade -f > libxfce4menu'. > My machine runs: > root@kg-v2# uname -a > FreeBSD kg-v2.kg4.no 8.2-STABLE FreeBSD 8.2-STABLE #4: Sat Jul 16 02:07:14 > CEST 2011 r...@kg-v2.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 > and the ports tree was updated today (26.1.2012). > > I also tried rebuilding (using portupgrade -f) a few other packages, to see > if xfce4-wm would upgrade afterwards: > libxfce4gui > libxfce4util > xfce4-conf > xfce4-desktop > xfce4-settings > > But that didn't help either. Have you run 'pkg-libchk -o | grep xcb-' from sysutils/bsdadminscripts? it should provide a list of ports that need to be re-built after the xcb-utils upgrade to 1.8. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: nautilus build failure
On Thu, Jan 26, 2012 at 4:05 PM, wrote:
>> On Thu, 26 Jan 2012 13:49:44 -0900 (AKST)
>> rfl...@acsalaska.net articulated:
>>
>>> > On Thu, 26 Jan 2012 16:36:54 -0500
>>>
>>> > I just ran "portclean -C" and then updated the ports tree, and
>>> > deleted all old files in "/usr/ports/distfiles". I then attempted
>>> > to build the port again. The exact same thing happened again. I
>>> > checked, and the "/usr/local/lib/libxcb-aux.la" file does not exist
>>> > on this system and I have no idea where to find and install it. The
>>> > system "make.conf" file is clean of any funkiness.
>>>
>>> % pkg_updating x11/xcb-util
>>> 20120116:
>>> AFFECTS: users of x11/xcb-util
>>> AUTHOR: ga...@freebsd.org
>>>
>>> x11/xcb-util was updated to 0.3.8 and was split in new modules.
>>> Dependencies were adjusted but main port symbols were moved to a
>>> single library, xcb-util.so. For this reason, all dependent ports
>>> must be recompiled.If you use portmaster, run:
>>>
>>> # portmaster -R -r xcb-util-0
>>>
>>> Or for portupgrade:
>>>
>>> # portupgrade -r xcb-util-0\*
>> I did exactly that; however, the situation still persists.
>
> Run this:
> find /usr/local/lib -type f -exec grep 'xcb-aux' {} +
>
> If that shows files, then those ports need to be upgraded first.
> However, if this shows libraries in /usr/local/lib/compat/pkg
> then delete those files. Libtool is being confused by outdated
> libraries and you need to figure out the culprit. A hint may
> be available in the lines above the failure message.
>
> -- Mel
While this works, I really continue to recommend Dominic Fandrey's
pkg_libcheck. It runs much faster as it runs parallel checks on
multiple files at the same time. Install sysutils/bsdadminscripts and
run 'pkg_libchk -o | grep xcb-' and rebuild all the ports reported.
--
R. Kevin Oberman, Network Engineer
E-mail: kob6...@gmail.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: mhonarc deprecated use of defined()
On Fri, Jan 27, 2012 at 3:57 AM, Peter Jeremy wrote: > On 2012-Jan-17 14:16:56 -0800, Rickie Kerndt wrote: >>Mhonarc when run with perl 10.14.2 complains about its deprecated use of >>defined(%a_hash). I've replaced these defined() where used (not many) as >>shown in the attached patch files. Is there any interest in updating the >>mhonarc port to fix this issue? > > "MAINTAINER=po...@freebsd.org" means no-one is maintaining that port. > If you are interested in maintaining it, I suggest you submit a PR > containing those patches and changing the maintainer to yourself. And, even if you are not willing to take on maintainership of the port, please submit this as a ports PR so it will not get lost and someone in the portsmgr group may get it committed when time is available. Still, if you are at all open to maintaining the port, please try taking over as maintainer. (If nothing else, updates from maintainers who are not commiters happen MUCH more quickly.) -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Nvidia optimus laptops
2012/2/1 Eyjólfur Kári Friðþjófsson : > Any plans on getting the nvidia optimus gpu´s working fulltime on BSD? > Its working on linux trough bumblebee 3.0 and virtualgl with some fake > xserver and its blazing fast! I can run the Unigine Heaven and tropics > benchmarks in opengl with tesselation faster then on directx11 on windows. > Thing is i would love to be able to switch from xbuntu to FreeBsd + xfce > but i hate having hardware thats not doing what its supposed to inside my > computer? > > SLI is another issue, getting multiple gpu´s to work together > Nvidia has been much better with their driver suppport then ATI but 3d > gaming is ofc not big on unix unless OSX gains some ground > > Anyway i would love to see someone port bumblebee 3.0 ( or the fork > ironhide) to the BSD platform and get it running with opengl 4 on BSD > fullspeed!!! I'd love to see this, too, but I think we'll need to wait until kib is finished with KMS and it's in9-stable (or, at very least in head before we can even think about Optimus support. Would be cool, though -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: print/ghostscript9: ./base/sjpx_openjpeg.c:169: error: too many arguments to function
On Tue, Feb 14, 2012 at 9:29 AM, Jerry wrote: > On Tue, 14 Feb 2012 16:33:07 + > Chris Rees articulated: > >> This has already been discussed on ports@, please don't cross-post. > > The problem has not been rectified as of yet. There is an open PR 165093 > filed against the port. I updated my ports tree about 7 hours ago and the fix was there. I've now built the new port on two systems (one amd64 and one i386) and had no problems. Looking at the repo, it appears the fix was made yesterday (2/13) at 21:48 and the Makefile should be CVS version 1.11. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pcre again
On Sun, Feb 19, 2012 at 2:04 PM, ajtiM wrote: > I did as I red on /usr/ports/UPDATING and when I checked pkg_libchk I have > many "misses" pcre related. > > Do I need run portmaster -r devel/pcre, please? It is quite possible that you will re-install quite a few ports that don't need it with 'portmaster -r'. I'd just re-build the ports called out in by 'pkg_libchk -o'. But you don't really need to do any immediately. The backup copy of libpcre.so.0 in /usr/local/lib/compat/pkg is not seen as that path is not checked by pkg_libchk. (I assume that is deliberate.) Still, it is probably a good idea to get them re-built. If some things are linked against two libraries, one of which uses .0 and the other using .1 which will break the executable as rtld will refuse to load it. OTOH, those who only install or update from packages after upgrading to a new release should have nothing to worry about. -- R. Kevin Oberman, Network Engineer E-mail: rkober...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: portupgrade -> portmaster Rosetta Stone?
On Sat, Feb 25, 2012 at 10:21 AM, Royce Williams wrote: > I noticed that the portupgrade port got returned to ports@ with this note: > > ports-mgmt/portupgrade > - Reassign to ports@ > please consider using ports-mgmt/portmaster > > Discussed with: bugmeister(eadler, linimon), ruby(swills, pgollucci) via > #bsdports > 22 Feb 2012 - pgollucci > http://www.freshports.org/ports-mgmt/portupgrade/ > > > To ease the transition, does anyone know of a Rosetta Stone table, or > "portmaster for native speakers of portupgrade"? Many things are just the same, but thee are a few 'gotcha's to be aware of. 1. There is no 'force' option for portmaster. You tell it to re-install a port and it does so. 2. If a directory is not specified (e.g. graphics/Imagemagick), the arguments are globs so that 'portmaster mplayer' will also run on mplayer-skins or any other installed port starting with mplayer. (I find this annoying, but Doug said that he got lots of requests for this behavior.) 3. portmaster ALWAYS behaves like -R was specified. The -R option in portmaster is very useful in some cases, but it is completely different from portupgrade. It is for Restart and is useful when updating lots of ports at once. 4. By default, portmaster will ask if you want ot delete the old distfile after installing an upgrade that uses a newer distfile. -D prevents this so you can run as close to non-stop as is possible. If you use -D, you may want to run 'portmaster --clean-distfiles' when you are all done. (portupgrade never attempts to clean up old distfiles and expects you to run portsclean for this.) Read the man page! Really! portmaster(8) has examples that will greatly simplify big jobs like completely reinstalling your ports and will clarify some of portmaster's behavior. I find portmaster vastly superior to portupgrade and highly recommended it before portupgrade was deprecated, though it did take a little getting used to, often because some things were so close to the same as portupgrade. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ImageMagick test failures?
On Sat, Mar 3, 2012 at 5:06 AM, Andriy Gapon wrote:
>
> I wonder if anyone else see something like this:
> http://www.imagemagick.org/discourse-server/viewtopic.php?f=2&t=20409&sid=ec7f098a613910103a6195ef86f18c45
I was seeing this ofr a while, but to seemed to stop happening after
some updates. Maybe some build option is triggering it or maybe
interaction with a dependent port? ImageMagick has a LOT of those.
Here are my options:
IMAGEMAGICK_16BIT_PIXEL=on "16bit pixel support"
IMAGEMAGICK_BZLIB=on "Bzlib support"
IMAGEMAGICK_DJVU=off "DJVU format support (needs threads)"
IMAGEMAGICK_DOT=off "GraphViz dot graphs support"
IMAGEMAGICK_FFTW=on "Discrete Fourier Transform support"
IMAGEMAGICK_FONTCONFIG=on "Fontconfig support"
IMAGEMAGICK_FPX=on "FPX format support"
IMAGEMAGICK_GSLIB=off "libgs (Postscript SHLIB) support"
IMAGEMAGICK_JBIG=on "JBIG format support"
IMAGEMAGICK_JPEG=on "JPG format support"
IMAGEMAGICK_JPEG2000=on "JPEG2000 format support"
IMAGEMAGICK_LCMS2=on "LCMS version 2 support"
IMAGEMAGICK_LCMS=on "LCMS version 1 support"
IMAGEMAGICK_LZMA=on "LZMA support"
IMAGEMAGICK_LQR=on "Liquid Rescale support"
IMAGEMAGICK_MODULES=on "Modules support"
IMAGEMAGICK_OPENEXR=off "OpenEXR support (needs threads)"
IMAGEMAGICK_OPENMP=off "OpenMP for SMP (needs threads)"
IMAGEMAGICK_PANGO=off "Pango support"
IMAGEMAGICK_PDF=on "PDF format support"
IMAGEMAGICK_PERL=on "Perl support"
IMAGEMAGICK_PNG=on "PNG format support"
IMAGEMAGICK_SVG=on "SVG format support (requires X11)"
IMAGEMAGICK_TESTS=on "Run bundled self-tests after build"
IMAGEMAGICK_TIFF=on "TIFF format support"
IMAGEMAGICK_TTF=on "Freetype support"
IMAGEMAGICK_WEBP=on "WEBP support"
IMAGEMAGICK_WMF=off "WMF format support"
THREADS=off "Threads support"
All ports are up to date and I am using gcc-4.2.1 and ghostscript9.
Builds pass all tests.
--
R. Kevin Oberman, Network Engineer
E-mail: kob6...@gmail.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: portupgrade -> portmaster after freebsd-update
On Sat, Mar 3, 2012 at 9:04 AM, Kurt Jaeger wrote: > Hi! > >> What is the proper portmaster commands in relation to freebsd-update? > [...] > > The portmaster man page lists the following list of commands in the > EXAMPLES section: > > Using portmaster to do a complete reinstallation of all your ports: > 1. portmaster --list-origins > ~/installed-port-list > 2. Update your ports tree > 3. portmaster -ty --clean-distfiles > 4. portmaster --check-port-dbdir > 5. portmaster -Faf > 6. pkg_delete -a > 7. rm -rf /usr/local/lib/compat/pkg > 8. Back up any files in /usr/local you wish to save, > such as configuration files in /usr/local/etc > 9. Manually check /usr/local and /var/db/pkg > to make sure that they are really empty > 10. Re-install portmaster > 11. portmaster `cat ~/installed-port-list` While this is the preferred procedure and I highly recommend it, it does far more that the portupgrade procedure in the handbook. The man page has a simpler (and more likely to leave old cruft lying around) procedure, as well. Alternatively you could use portmaster -a -f -D to do an ``in place'' update of your ports. If that process is interrupted for any reason you can use portmaster -a -f -D -R to avoid rebuilding ports already rebuilt on previous runs. However the first method (delete everything and rein- stall) is preferred. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ImageMagick test failures?
On Sat, Mar 3, 2012 at 12:25 PM, Robert Huff wrote: > > Andriy Gapon writes: > >> Thank you very much for your detailed information! >> It seems that IMAGEMAGICK_GSLIB is the culprit here. > > That option is set for me as well. Hmm. gslib is off by default. If it is on for you, you turned it on. Still, It once did work. I have used it, though it's been years. I've been using ImageMagick for about a quarter century, originally on VMS. It's grown and evolved quite a bit since it was supported at E.I. DuPont Chemical, though I think Christy, the original author is still involved. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: How to submit a new port along with its distfile?
On Fri, Mar 2, 2012 at 10:59 PM, Conrad J. Sabatier wrote: > If anyone's interested, the package is call mkreadmes-1.0. It's a C > language version of the port's collection's "make readmes" (or, if you > will, the perl "make_readmes" script under the Tools directory). I > wrote this because I was very dissatisfied with the speed of rebuilding > the README.html files after I update my ports tree. This new tool I've > written cuts the time down to practically nothing. I can now rebuild > all the README.html files for the entire ports tree in less than 30 > seconds. Depending on system load, I've actually seen it run in as > little as @ 15 seconds. > > If you want to try it before it becomes an official port, it's already > available on Sourceforge right now. It should compile and install very > easily on any FreeBSD system, even without the port framework wrapper. > > The source archive is available at: > > http://sourceforge.net/projects/mkreadmes/files/mkreadmes-1.0.tar.bz2/download > > A README file is included in the distribution. Online help is also > available via the "-h" command line option. > > Please don't hesitate to send me any questions, comments, suggestions, > bug reports, etc. Conrad, Thanks so much for mkreadmes. It works as advertised and this is the first time in years that I have built all of the READMEs because it just took way, way too long to do so before mkreadmes. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: portaudit pubkey
On Mon, Mar 12, 2012 at 10:54 AM, Jakub Lach wrote: > Thanks for such attention. > > I'm using portsnap with main portsnap server. > >> Even after deleting everything in ports-mgmt/portaudit >> and doing a new csup with the second commit I was >> still getting the above error. > > Exactly. Now, since I've finally found pubkey (I was > looking in wrong places, and yesterday google's 0 hits > with "portaudit.pubkey" didn't help either), I have a > feeling that my problem is over, thanks for help. The easy fix is just 'portaudit -F'. then everything went fine on all of my systems. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: portaudit pubkey
On Mon, Mar 12, 2012 at 3:25 PM, Jakub Lach wrote: > If I recall correctly 'portaudit -Fa' didn't > change anything for me, and some attempt > at updating of portaudit bombed after > portaudit have been already deleted, so > without pubkey I couldn't install portaudit > again. > > But I may be wrong, I haven't exactly > paid attention from the beginning.. While I didn't think it relevant, maybe it is significant that I always did 'portmaster portaudit and THEN did ' portaudit -F' and re-ran portmaster. I don't know if portmaster vs. portupdate is relevant, either. Oddly, if I updated multiple ports (portmaster portaudit ImageMagick), the last port, regardless of what it was, reported this error. Of course, ports updated before portaudit worked, but if portaudit was the last port to be updated, it failed. If I updated ImageMagick AFTER portaudit, portaudit succeeded and ImageMagick failed. But, in either case 'portaudit -F' allowed the remaining port(s) to build and install normally. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: security/gnutls update when...
On Sat, Mar 24, 2012 at 10:29 AM, Jason Hellenthal wrote: > > Apparently this port has fell two versions behind. Is there anything > that is going to happen to update it to the current stable version ? > > > These advisories have been out for a week now. And the current version > is 2.12.18. > > > Database created: Sat Mar 24 13:15:03 EDT 2012 > Affected package: gnutls-2.12.16 > Type of problem: libtasn1 -- ASN.1 length decoding vulnerability. > Reference: > http://portaudit.FreeBSD.org/2e7e9072-73a0-11e1-a883-001cc0a36e12.html > > Affected package: gnutls-2.12.16 > Type of problem: gnutls -- possible overflow/Denial of service > vulnerabilities. > Reference: > http://portaudit.FreeBSD.org/aecee357-739e-11e1-a883-001cc0a36e12.html > > 2 problem(s) in your installed packages found. > > > > -- > ;s =; Note that one of these problems is with libtasn1 and is not a gnutls problems at all. So updating libtasn1actually fixes this one, although the other does require an update to a version of gnutls that has yet to be ported. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Master Site problem
On Tue, Mar 27, 2012 at 10:15 AM, Chris Rees wrote:
> On 27 March 2012 17:12, Olli Hauer wrote:
>> On 2012-03-27 18:53, Paul Schmehl wrote:
>>> I'm trying to create a new port for a Perl module: CIF::Client. You can
>>> find it here:
>>> <http://search.cpan.org/~saxjazman/CIF-Client-0.05/lib/CIF/Client.pm>
>>>
>>> I can't figure out how to define the Master Site so this thing will
>>> download. Hopefully one of you perl cpan gurus can help.
>>>
>>
>> Hi Paul,
>>
>> try the following
>>
>> a)
>> PORTNAME= CIF-Client
>> MASTER_SITES= CPAN
>> MASTER_SITE_SUBDIR= CPAN:SAXJAZMAN/cif
>>
>> b)
>> PORTNAME= cif-client
>> MASTER_SITES= CPAN
>> MASTER_SITE_SUBDIR= CPAN:SAXJAZMAN/cif
>> DISTNAME= CIF-Client-${PORTVERSION}
> ^^^
>
> I thought we tried to keep CaPiTaLiSaTiOn of PORTNAME consistent with
> upstream, just having the origin lowercase, or am I mistaken?
I believe that by our conventions it should be"
PORTNAME= p5-CIF-Client
it's much easier to deal with perl version updates when you can just
'portmanager p5-'. Currently I use about 100 perl ports and only two
fail to follow this convention and they are top-level apps that happen
to be written in perl (net-snmp and dvd::rip).
--
R. Kevin Oberman, Network Engineer
E-mail: kob6...@gmail.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: security/openssl so bump w/o mention in UPDATING
On Thu, Apr 12, 2012 at 4:23 AM, Oliver Heesakkers wrote: > security/openssl was brought up to 1.0.1 recently which includes bumping > OPENSSL_SHLIBVER from 7 to 8. > > Which means, that in order not to break surprisingly many ports on my > desktop > I have to "portmaster -r" this port. > > "portmaster -w" might have also done the trick and I'll leave mentions of > other ports-mgmt tools to whomever who will commit this to UPDATING as I > believe should happen. Sorry to sound like a broken record, but using 'portmaster -r' for this is using a .50 cal. machine gun to kill a fly. Serious over-kill! Install sysutils/bsdadminscripts, update the port (with -w if you want) and use 'pkg_libchk -o'. It will l list just the ports that actually link to the library in question. Then just re-install these ports. The number of ports needing re-installation will often drop from hundreds to a dozen or so. Not many things depend directly on openssl, but those ports' libraries are linked to a great many more. Just '-w' is of limited value if you update ports (and it appears that you do) as you will start getting rtld errors when an executable links to two shareables, one of which is linked to the old version and one to the new. For something like openssl, this will happen a lot and getting rid of references to the old openssl shareable is the only way to fix it. Because a fer ports do their own linking to shareables (java comes to mind), pkg_chklib will generate a few false positives. If you pipe the output to a grep for the shareable in question, you can avoid updating ports that don't need it. As pkg_libchk is just a shell script and one that can be a huge time-saver, I think I may start pushing to either be integrated into portmaster (I doubt Doug will go for that and I probably wouldn't, either) or made a standard tool for the system. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: security/openssl so bump w/o mention in UPDATING
On Thu, Apr 12, 2012 at 11:19 AM, Oliver Heesakkers wrote: > Kevin Oberman schreef op 12.04.2012 18:13: >> >> On Thu, Apr 12, 2012 at 4:23 AM, Oliver Heesakkers >> wrote: >>> >>> security/openssl was brought up to 1.0.1 recently which includes bumping >>> OPENSSL_SHLIBVER from 7 to 8. >>> >>> Which means, that in order not to break surprisingly many ports on my >>> desktop >>> I have to "portmaster -r" this port. >>> >>> "portmaster -w" might have also done the trick and I'll leave mentions of >>> other ports-mgmt tools to whomever who will commit this to UPDATING as I >>> believe should happen. >> >> >> Sorry to sound like a broken record, but using 'portmaster -r' for >> this is using a .50 cal. machine gun to kill a fly. Serious over-kill! >> >> Install sysutils/bsdadminscripts, update the port (with -w if you >> want) and use 'pkg_libchk -o'. It will l list just the ports that >> actually link to the library in question. Then just re-install these >> ports. The number of ports needing re-installation will often drop >> from hundreds to a dozen or so. Not many things depend directly on >> openssl, but those ports' libraries are linked to a great many more. >> >> Just '-w' is of limited value if you update ports (and it appears that >> you do) as you will start getting rtld errors when an executable links >> to two shareables, one of which is linked to the old version and one >> to the new. For something like openssl, this will happen a lot and >> getting rid of references to the old openssl shareable is the only way >> to fix it. >> >> Because a fer ports do their own linking to shareables (java comes to >> mind), pkg_chklib will generate a few false positives. If you pipe the >> output to a grep for the shareable in question, you can avoid updating >> ports that don't need it. >> >> As pkg_libchk is just a shell script and one that can be a huge >> time-saver, I think I may start pushing to either be integrated into >> portmaster (I doubt Doug will go for that and I probably wouldn't, >> either) or made a standard tool for the system. > > > Yes, you're quite right. I'll rephrase: > > IMHO *something* should be said in UPDATING, what exactly is up to > maintainer / committer(s). Indeed! I was a bit surprised that there was no entry. And, to accurately (and less hyperbolicly) state the advantage of using pkg_libchk, I am re-installing 64 ports while 'portmaster -r openssl' would have updated 364. Not quite the disparity I have seen with some ports that bumped shareable versions, but still very significant. (The system I am using is my old laptop with 1380 ports including gnome2 installed, so it's near worst case, I suspect.) -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: port variants
2012/4/13 Konstantin Tokarev : > > > 13.04.2012, 23:55, "Chris Inacio" : >> On Apr 13, 2012, at 3:39 PM, Freddie Cash wrote: >> >>> On Fri, Apr 13, 2012 at 12:04 PM, Chris Inacio wrote: >>>> I was recently asked to do some FreeBSD ports support work. I mostly use >>>> a >>>> Mac and the MacPorts system. MacPorts has the concept of a variant for a >>>> port, but I can't find the analogue in the FreeBSD system. >>>> >>>> Does the FreeBSD ports system have the concept of a variant? If so, can >>>> someone point me in the right direction on how to create one? >>> Describing what a "variant" is, how it works in MacPorts, and what you >>> are trying to do would help a lot. :) >>> >>> The closest guess I could make would be "slave port", but I don't >>> think that works the same way. >> >> Sorry, you're right. >> >> For example, a port of say Emacs could have a variant of X11. >> >> So Emacs or Emacs+X11. >> >> The X11 variant would (somewhat obviously) include building regular Emacs >> but also the X11 toolbar etc. while Emacs wouldn't include any X11 features >> (& dependencies). >> >> On the Mac, we can build universal binaries (PowerPC, ia32, and x86_64), at >> the cost of disk space. So we can build almost any package with the >> +universal variant. >> >> Is that a reasonable explanation? > > Seems like you need makefile options: > > http://www.freebsd.org/doc/en/books/porters-handbook/makefile-options.html While I think makefile-options is the way to go, I should also point out that for the specific case of emacs and X11, it is not used due to the very large differences. Other "variants" are handled via options, but there are separate emacs and emacs-nox11 ports. Most obviously, all of the emacs options are X11 related and there is no way that I know to have two sets of options with one list dependent on the other. If there are only a coupe of cases of this, it may be noted on the options like: THREADS " Build with thread support" On \ FOO"Foo support (requires THREADS)" OFF \ The port maintainer/developer has to make a call as to which approach is more practical, but I suspect portmgr@ will press for maximum use of makefile-options. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: security/openssl moved from libssl.so.7 to libssl.so.8 on 2012/04/11
On Tue, Apr 17, 2012 at 5:23 AM, Bryan Drewery wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > > On 4/17/2012 12:50 AM, Jeff Kletsky wrote: > >> Should libssl.so.7 have been retained somehow? >> >> I upgraded using portmaster, it that provides any clues as to why it was >> or wasn't. >> > > Using -w with portmaster will retain the old file in > /usr/local/lib/compat/pkg > > After the port is built, if the -w option is being used, all shared > libraries installed by the old port (if any) will be saved to > /usr/local/lib/compat/pkg. After installation if there are any new > files > with the same names as those in /usr/local/lib/compat/pkg the old files > will be deleted, and ldconfig(8) will be run via /etc/rc.d/ldconfig. I have dropped Dirk a note asking for him to add a note in UPDATING. This should really be done whenever a common sharable get a version bump. It can be a bit of a shock when lots of security related stuff starts crashing after what looks like a minor update to a port. As I always point out, re-building all dependent ports does fix things, but it results in updating many ports that don't need it as they don't link to the sharable but are simply dependent on a port that does. In the case of my laptop I think I had about 40 ports that actually linked to one of the updated sharables, but about 350 that would have been re-built if i had gone the "all dependent ports" route. If you want to just build the ports that actually need it, install sysutils/bsdadminscripts and use 'pkg_libchk -o | grep -E "crypt.so|ssl.so"' (or just 'pkg_libchk -o', but you will likely get false positives from ports that load sharables themselves instead of using rtld to do it). Yes, '-w' will work in the short term, but you still need to re-build ports fairly soon as you will hit a case where an executable links to two sharables, one of which is from a port that was already installed and links to the old sharable and one which was updated and links to the new one. That executable will no longer run. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [HEADS UP] Xorg 7.5.2 merge.
On Sat, Apr 21, 2012 at 3:22 PM, Martin Wilke wrote: > Hi, > > Howdy Guys, > > First of all we apologize for the long waiting time. Xorg 7.5.2 is > completely finished last issues were fixed by kwm@, and the exp-run > was also fine, I'm preparing the merge now and will commit it by today. > So I think you should monitor the CVS commits, ports and x11 mailing > list to make sure you don't report a duplicate problems. Congratulations, guys! I've been waiting for this for a while and I'm sure many will join me in thanking all of those that have put so much effort into making it happen! Embarrassingly, I just sent the list a message about the need to run xorg-devel for many things (like Intel KMS) and how it was not in ports. I hit "Send" and this message showed up. Any idea about when/if Intel KMS might make it out of test mode? (I know, I should let you enjoy getting this done before asking for more.) -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Foswiki port
On Tue, Apr 24, 2012 at 12:06 PM, Doug Sampson wrote:
> Hello-
>
> When will Foswiki be updated to 1.1.4? It's currently at 1.1.3 and doesn't
> work with Perl 5.14 but 1.1.4 does. Version 1.1.5 is coming out soon and I'd
> like to upgrade to 1.1.4 and make sure all works smoothly before version
> 1.1.5 gets released.
I submitted the update to 1.1.5 to ports a while ago. Just waiting for a commit.
See PR ports/166399
Updated patch for foswiki 1.1.5:
diff -urN foswiki/Makefile foswiki-new/Makefile
--- foswiki/Makefile 2012-01-02 03:34:59.0 -0800
+++ foswiki-new/Makefile 2012-03-24 22:44:47.0 -0700
@@ -6,7 +6,7 @@
#
PORTNAME= foswiki
-PORTVERSION= 1.1.3
+PORTVERSION= 1.1.5
CATEGORIES= www
MASTER_SITES= SF
DISTNAME= Foswiki-${PORTVERSION}
diff -urN foswiki/distinfo foswiki-new/distinfo
--- foswiki/distinfo 2011-04-19 03:08:02.0 -0700
+++ foswiki-new/distinfo 2012-03-24 23:10:02.0 -0700
@@ -1,2 +1,2 @@
-SHA256 (foswiki/Foswiki-1.1.3.tgz) =
76d81d10765fefb0e17872482b778fab446d6e357a62ba87aba6eb36d4398b7d
-SIZE (foswiki/Foswiki-1.1.3.tgz) = 13263991
+SHA256 (foswiki/Foswiki-1.1.5.tgz) =
7868d32bd3852c7772f88c3ccf6289639d4026adeeef2353c2bbe5e774d1e237
+SIZE (foswiki/Foswiki-1.1.5.tgz) = 15306439
--
R. Kevin Oberman, Network Engineer
E-mail: kob6...@gmail.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ImageMagick upgrade problem
> Em Ter, 2010-11-23 Ã s 17:50 +, David Southwell escreveu: > > > > Puzzled > > > > I have perl installed with threads but getting the following upgrade > > problem > > with graphics/ImageMagick. The upgrade fails to recognise reality - Perl is > > installed with threads! > > with OpenEXR or OpenMP I get the same problem: > > Make sure that perl is compiled with threads and. > > for me I solved the problem by > defining in /etc/make.conf.PERL_THREADED=true > > it works, but the real solution is to fix the port > either in IMagemagick or in perl ... Just 'make PERL_THREADED=true' is probably easier, but the port is clearly broken. The logic is very oddly set out, but it relies on the value of PERL_THREADED which neither the Makefile nor any of the .Mk files defines. I assume that there was supposed to be some test of whether perl supports threading that never quite made it. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ImageMagick upgrade problem
> From: David Southwell > Date: Tue, 23 Nov 2010 22:15:58 + > > > > Em Ter, 2010-11-23 Ã s 17:50 +, David Southwell escreveu: > > > > Puzzled > > > > > > > > I have perl installed with threads but getting the following upgrade > > > > problem with graphics/ImageMagick. The upgrade fails to recognise > > > > reality - Perl is installed with threads! > > > > > > > with OpenEXR or OpenMP I get the same problem: > > > Make sure that perl is compiled with threads and. > > > > > > for me I solved the problem by > > > defining in /etc/make.conf.PERL_THREADED=true > > > > > > it works, but the real solution is to fix the port > > > either in IMagemagick or in perl ... > > > > Just 'make PERL_THREADED=true' is probably easier, but the port is > > clearly broken. The logic is very oddly set out, but it relies on the > > value of PERL_THREADED which neither the Makefile nor any of the .Mk > > files defines. I assume that there was supposed to be some test of > > whether perl supports threading that never quite made it. > Tried the /etc/make.conf PERL_THREADED=true > but still get the same result in graphics/ImageMagick: > > dns1# make clean > ===> Cleaning for perl-threaded-5.8.9_4 > ===> Cleaning for ImageMagick-6.6.5.10 > dns1# make > ===> ImageMagick-6.6.5.10 OpenEXR requires threads. . Perl is non-threaded. > Reinstall Perl with threads or undefine WITH_IMAGEMAGICK_PERL. > *** Error code 1 I don't know why it is happening, but /etc/make.conf did not help. I had to define it on the command lines: $ make PERL_THREADED=true $ make deinstall PERL_THREADED=true $ make reinstall PERL_THREADED=true This worked fine, but I don't see why it is different from putting it in /etc/make.conf. Then again, I am way way far from being a make(1) expert. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
New version of OpenSC not compatible with current OpenSSH port
Good day, I just learned that OpenSC 0.12.0, recently committed to ports is not compatible with openssh-portable 5.2. It requires at least 5.3. As a result, upgrading opensc is a serious problem for those of us depending on SmartCards for SSH keys. Could you mitigate this by: Adding a note to UPDATING that upgrading opensc will break integration with OpenSSH Restoring the openssh-portable port to its state before the OPENSC and OPENSCPINPATCH configuration options (along with the scardpin.patch file) were removed? Also, does anyone know if work is going on to port 5.3p1 or more recent? The current released version is 5.6p1. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Unable to configure dirmngr after libksba upgrade
After I upgraded libksba to 1.2.0, I attempted to re-build dirmngr, but all of my systems are failing due to failing to detect LDAP. checking whether LDAP via "-lldap" is present and sane... no checking whether LDAP via "-lldap -llber" is present and sane... no checking whether LDAP via "-lldap -llber -lresolv" is present and sane... no checking whether LDAP via "-lwldap32" is present and sane... no checking for ANSI C header files... (cached) yes checking for string.h... (cached) yes checking locale.h usability... yes checking locale.h presence... yes checking for locale.h... yes checking for an ANSI C-conforming const... yes checking for inline... inline checking for size_t... yes checking return type of signal handlers... void checking whether sys_siglist is declared... yes checking for byte typedef... no checking for ushort typedef... yes checking for ulong typedef... no checking for struct sigaction... yes checking for sigset_t... yes checking for sys/stat.h... (cached) yes checking for unistd.h... (cached) yes checking direct.h usability... no checking direct.h presence... no checking for direct.h... no checking if mkdir takes one argument... no checking for memicmp... no checking for stpcpy... yes checking for strsep... yes checking for strlwr... no checking for strtoul... yes checking for memmove... yes checking for stricmp... no checking for strtol... yes checking for memrchr... yes checking for isascii... yes checking for timegm... yes checking for getrusage... yes checking for setrlimit... yes checking for stat... yes checking for setlocale... yes checking for flockfile... yes checking for funlockfile... yes checking for funopen... yes checking for fopencookie... no checking for gmtime_r... yes checking for getaddrinfo... yes checking for strtoull... yes checking for mmap... yes checking for canonicalize_file_name... no configure: *** *** You need a LDAP library to build this program. *** Check out ***http://www.openldap.org *** for a suitable implementation. *** configure: error: *** *** Required libraries not found. Please consult the above messages *** and install them before running configure again. *** ===> Script "configure" failed unexpectedly. Please report the problem to u...@ueo.co.jp [maintainer] and attach the "/usr/ports/security/dirmngr/work/dirmngr-1.1.0/config.log" including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. an `ls /var/db/pkg`). *** Error code 1 Stop in /usr/ports/security/dirmngr. *** Error code 1 I certainly do have openldap-client installed. I even re-installed it, just to make sure nothing had been stepped on. I have libldap and liblber in /usr/local/lib/ The first two attempts fail with: /usr/local/lib/libldap.so: undefined reference to `fetchGetURL' Any idea what may be going wrong? -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Unable to configure dirmngr after libksba upgrade
> Date: Mon, 28 Mar 2011 11:22:37 -0700 > From: Doug Barton > > On 03/28/2011 11:13, Kevin Oberman wrote: > > I certainly do have openldap-client installed. I even re-installed it, > > just to make sure nothing had been stepped on. I have libldap and > > liblber in/usr/local/lib/ > > > > The first two attempts fail with: > > /usr/local/lib/libldap.so: undefined reference to `fetchGetURL' > > > > Any idea what may be going wrong? > > I haven't tested the theory yet, but can you check if openldap has been > built with the FETCH option, and if not, try enabling it and see if that > helps? Thanks, but no joy. It was built with fetch(3) support. I'll look more closely at the log in a bit, but I'm going to be tied up for an hour or so with other issues. (Still have a network to engineer.) -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Unable to configure dirmngr after openldap upgrade
> Date: Mon, 28 Mar 2011 11:47:49 -0700 > From: Doug Barton > > This has nothing to do with libksba, it's just a coincidence that > bumping the PORTREVISION on dirmngr for the libksba update caused you to > rebuild dirmngr against an up to date openldap. > > Reverting to openldap-client-2.4.24 allows dirmngr to build, thus I've > changed the subject line of this message. The presence of the FETCH > option (which is what I always use anyway) doesn't improve the > situation, FYI. > > > Doug > > > On 03/28/2011 11:22, Kevin Oberman wrote: > > After I upgraded libksba to 1.2.0, I attempted to re-build dirmngr, but > > all of my systems are failing due to failing to detect LDAP. > > > > checking whether LDAP via "-lldap" is present and sane... no > > checking whether LDAP via "-lldap -llber" is present and sane... no > > checking whether LDAP via "-lldap -llber -lresolv" is present and sane... no > > checking whether LDAP via "-lwldap32" is present and sane... no > > checking for ANSI C header files... (cached) yes > > checking for string.h... (cached) yes > > checking locale.h usability... yes > > checking locale.h presence... yes > > checking for locale.h... yes > > checking for an ANSI C-conforming const... yes > > checking for inline... inline > > checking for size_t... yes > > checking return type of signal handlers... void > > checking whether sys_siglist is declared... yes > > checking for byte typedef... no > > checking for ushort typedef... yes > > checking for ulong typedef... no > > checking for struct sigaction... yes > > checking for sigset_t... yes > > checking for sys/stat.h... (cached) yes > > checking for unistd.h... (cached) yes > > checking direct.h usability... no > > checking direct.h presence... no > > checking for direct.h... no > > checking if mkdir takes one argument... no > > checking for memicmp... no > > checking for stpcpy... yes > > checking for strsep... yes > > checking for strlwr... no > > checking for strtoul... yes > > checking for memmove... yes > > checking for stricmp... no > > checking for strtol... yes > > checking for memrchr... yes > > checking for isascii... yes > > checking for timegm... yes > > checking for getrusage... yes > > checking for setrlimit... yes > > checking for stat... yes > > checking for setlocale... yes > > checking for flockfile... yes > > checking for funlockfile... yes > > checking for funopen... yes > > checking for fopencookie... no > > checking for gmtime_r... yes > > checking for getaddrinfo... yes > > checking for strtoull... yes > > checking for mmap... yes > > checking for canonicalize_file_name... no > > configure: > > *** > > *** You need a LDAP library to build this program. > > *** Check out > > ***http://www.openldap.org > > *** for a suitable implementation. > > *** > > configure: error: > > *** > > *** Required libraries not found. Please consult the above messages > > *** and install them before running configure again. > > *** > > ===> Script "configure" failed unexpectedly. > > Please report the problem to u...@ueo.co.jp [maintainer] and attach the > > "/usr/ports/security/dirmngr/work/dirmngr-1.1.0/config.log" including the > > output of the failure of your make command. Also, it might be a good idea to > > provide an overview of all packages installed on your system (e.g. an `ls > > /var/db/pkg`). > > *** Error code 1 > > > > Stop in /usr/ports/security/dirmngr. > > *** Error code 1 > > > > I certainly do have openldap-client installed. I even re-installed it, > > just to make sure nothing had been stepped on. I have libldap and > > liblber in /usr/local/lib/ > > > > The first two attempts fail with: > > /usr/local/lib/libldap.so: undefined reference to `fetchGetURL' > > > > Any idea what may be going wrong? > > > > -- > > Nothin' ever doesn't change, but nothin' changes much. > -- OK Go > > Breadth of IT experience, and depth of knowledge in the DNS. > Yours for the right price. :) http://SupersetSolutions.com/ > Yup. openldap-client-2.4.24 does fine. Looks like a bug in 2.4.25. I'll take a look at CHANGES and see if I can figure out what broke the inclusion of fetch(3) support if I get a bit of time. Thanks! -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Unable to configure dirmngr after openldap upgrade
> Date: Mon, 28 Mar 2011 16:30:03 -0700 > From: Doug Barton > > On 03/28/2011 14:20, Xin LI wrote: > > On 03/28/11 13:57, Doug Barton wrote: > >> On 03/28/2011 13:48, Xin LI wrote: > >>> On 03/28/11 12:42, Kevin Oberman wrote: > >>>> Yup. openldap-client-2.4.24 does fine. Looks like a bug in 2.4.25. I'll > >>>> take a look at CHANGES and see if I can figure out what broke the > >>>> inclusion of fetch(3) support if I get a bit of time. > >>> > >>> It seems that libldif now referenced the fetch support, and ironically > >>> it seem be a bug but a feature :( > >>> > >>> I have decided to disable FETCH support from now on, since it's likely > >>> to bring more problems. > >>> > >>> (If you would prefer to fix the problem for this specific problem, I > >>> think adding a '-lfetch' would be sufficient; but, it seems to be > >>> undesirable to depend fetch(3) unconditionally for all programs that > >>> uses openldap). > > > >> I know next to nothing about how the openldap-client stuff works, so I'm > >> sorry if these questions are silly. :) The biggest question is, does > >> dirmngr compile after your change? The other question is that the only > >> reason I have openldap installed at all is so that gnupg can use it to > >> fetch keys from ldap keyservers. Will this still work when the FETCH > >> option is no longer present? > > > > hmm... how do I test fetching from an ldap keyserver? > > I'll save you the trouble. :) I got your latest update and tested both > scenarios myself, and the answer is that they both work. > > So now the question is, should the FETCH OPTION be removed altogether? I > imagine that a lot of users will be at least as confused as I, and word > is that PRs for other ports are already showing up. No joy. I updated openldap-client to 2.4.25_1 and than tried to rebuild dirmngr. Same error as I had before: /usr/local/lib/libldap.so: undefined reference to `fetchGetURL' Back to 2.2.24. Thanks for trying to get this fixed up. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Unable to configure dirmngr after openldap upgrade
> Date: Tue, 29 Mar 2011 11:57:52 -0700 > From: Doug Barton > > On 03/29/2011 11:54, Kevin Oberman wrote: > > No joy. I updated openldap-client to 2.4.25_1 and than tried to rebuild > > dirmngr. Same error as I had before: > > /usr/local/lib/libldap.so: undefined reference to `fetchGetURL' > > You have to disable the FETCH option. If you're building it in the port > directory, type 'make config'. If you're using portmaster, add > --force-config to the command line. In the immortal words of Homer, "Doh!" (Homer Simpson, that is). -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Call for Testers: VirtualBox 4.0.6
> Date: Mon, 09 May 2011 05:57:05 -0700 > From: Yuri > Sender: owner-freebsd-emulat...@freebsd.org > > I think 4.0.6 is quite stable now. Is it really less stable than the > current version in ports 3.2.12? > Why don't you at least put them into ports/emulators repository with > -devel suffix like many other ports do? So that there is no need to go > through the third party repository. 4.0.6 is still not as robust for me as 3.2.12, but it's now close and the added features still make it a win for me. I have not had an actual crash with 4.0.6, but I have had VMs simply deadlock. The problems I have seen are all upstream, not FreeBSD specific. I see the same issues when I use my Ubuntu VM running on Windows7. 4.0.6 is MUCH more stable than 4.0.4. I think it's reasonable to update the port. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Skype with sound and video support :)
> Date: Tue, 17 May 2011 10:38:58 +0300 > From: Ion-Mihai Tetcu > Sender: owner-freebsd-emulat...@freebsd.org > > Hi, > > > As you may have noticed skype ports were updated a few days ago. > > All skype ports were moved to net-im/: > - skype12: unchanged, very old version (for FreeBSD 6) > - skype20: last version with OSS support, that used to live in > net/skype; the DISTFILE is gone from the vendor but if you happen to > have it it would be a way of having sound w/o a need to upgrade your > base OS > - [RECOMANDED] skype: currently at 2.1.0.81 and the best supported > - skype-devel: currently at 2.2.0.25, sounds is OK, video doesn't work > > In order to run either skype or skype-devel with fully working sound > you need: > - to run fc10 (most probably, please report what you can run with fc4): > (OVERRIDE_LINUX_BASE_PORT=f10,OVERRIDE_LINUX_NONBASE_PORTS=f10 > in /etc/make.conf for systems that doesn't have it as default) > - In order for Skype to work OK, you need your kernel and modules to be: > - post 2011-05-03 in on HEAD > - post 2011-05-08 in on 7,8-STABLE > The port tries to catch if your system version is too old, but there's > a ~3months window where because of a lack of OSVERSION bump, this is > not possible. So please check; and PLEAE READ THE PKG_MESSAGE for > setup details. For how to update your kernel/world, see: > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig.html > > IF YOUR OSVERSION IS NOT NEW ENOUGH, SOUND (ESPECIALLY MIC) WON'T WORK. > > If you run into problems, at very least we need to know the output of: > > $ uname -a; sysctl compat.linux | head -2; grep OVERRIDE_LINUX_ > /etc/make.conf; cat /compat/linux/etc/alsa/pcm/pcm-oss.conf > > the skype version you are using, and hardware details (eg. webcam) if > related. I most probably will ignore any mail not containing this info > since without it it's impossible to help. > > Please test your sound /video setup outside skype before blaming skype / > mailing me. Many thanks for all of the work that went into getting a modern version of Skype working! Please put the information in this message (or at least most of it) into ports/UPDATING so a few less people running old kernels will be bitten by the installation of the new Skype port. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Ruby 19 install(?) failure
I just tried upgrading ruby to lang/ruby19 as per ports/UPDATING. Looks like build just patches and the 'make install' does most of the real work. In any case, it fails. cc -shared -o ../../.ext/amd64-freebsd8/zlib.so zlib.o -L. -L../.. -L. -rdynamic -Wl,-soname,../../.ext/amd64-freebsd8/zlib.so -Wl,-R -Wl,/usr/local/lib -L/usr/local/lib -lruby19 -lz -lthr -lrt -lcrypt -lm -L/usr/local/lib -rpath=/usr/lib:/usr/local/lib -pthread -lc making ruby19 make: don't know how to make NO_DEPENDS. Stop *** Error code 2 Running 8.2-Stable of Aug 19. Any idea what's wrong? Thanks! -- R. Kevin Oberman, Network Engineer - Retired E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Ruby 19 install(?) failure
On Tue, Aug 23, 2011 at 2:15 PM, Kevin Oberman wrote: > I just tried upgrading ruby to lang/ruby19 as per ports/UPDATING. > Looks like build just patches and the 'make install' does most of the > real work. In any case, it fails. > > cc -shared -o ../../.ext/amd64-freebsd8/zlib.so zlib.o -L. -L../.. -L. > -rdynamic -Wl,-soname,../../.ext/amd64-freebsd8/zlib.so -Wl,-R > -Wl,/usr/local/lib -L/usr/local/lib -lruby19 -lz -lthr -lrt -lcrypt > -lm -L/usr/local/lib -rpath=/usr/lib:/usr/local/lib -pthread -lc > making ruby19 > make: don't know how to make NO_DEPENDS. Stop > *** Error code 2 > > Running 8.2-Stable of Aug 19. > > Any idea what's wrong? > Thanks! Now I'm very confused. After the same failure three times, I tied a manual "make install" and it worked. I then re-ran the "portmaster -o lang/ruby19 /lang/ruby18 and it semed to be OK, but when I ran the "portmaster -R -r lang/ruby-1.9, it tried to install ruby18-gems and that tried to re-install ruby18. Am I missing something? -- R. Kevin Oberman, Network Engineer - Retired E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Ruby 19 install(?) failure
On Aug 23, 2011 5:33 PM, "Steve Wills" wrote: > > Hi, > > On 08/23/11 18:08, Kevin Oberman wrote: > > On Tue, Aug 23, 2011 at 2:15 PM, Kevin Oberman wrote: > >> I just tried upgrading ruby to lang/ruby19 as per ports/UPDATING. > >> Looks like build just patches and the 'make install' does most of the > >> real work. In any case, it fails. > >> > >> cc -shared -o ../../.ext/amd64-freebsd8/zlib.so zlib.o -L. -L../.. -L. > >> -rdynamic -Wl,-soname,../../.ext/amd64-freebsd8/zlib.so -Wl,-R > >> -Wl,/usr/local/lib -L/usr/local/lib -lruby19 -lz -lthr -lrt -lcrypt > >> -lm -L/usr/local/lib -rpath=/usr/lib:/usr/local/lib -pthread -lc > >> making ruby19 > >> make: don't know how to make NO_DEPENDS. Stop > >> *** Error code 2 > >> > >> Running 8.2-Stable of Aug 19. > >> > >> Any idea what's wrong? > >> Thanks! > > > > Now I'm very confused. After the same failure three times, I tied a > > manual "make install" > > and it worked. I then re-ran the "portmaster -o lang/ruby19 > > /lang/ruby18 and it semed to be OK, but when I ran the "portmaster -R > > -r lang/ruby-1.9, it tried to install ruby18-gems and that tried to > > re-install ruby18. > > > > Am I missing something? > > My apologies for the trouble. Can you tell me what version of FreeBSD > you're on and what other packages you have installed? > > Thanks, > Steve As stated, 8-Stable of Aug. 19. I should have also mentioned that it's an amd64 system. I have about 900 ports installed including a full gnome system and a number of multimedia ports inc. ffmpeg, handbrake, mplayer, lame, avidemux, and several that don't come to mind. If you need it, I can send the full list when I get back to my system. Thanks! R. Kevin Oberman, Network Engineer Retired kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Please test: mplayer 1.0 rc2
> Hi, > > the mplayer developers recently released the 1.0 rc 2 version of their > well known product. > I updated the mplayer and mencoder ports accordingly and attached them > to this mail. > Any feedback/patches are appreciated before I'm going to send-pr this. I built mplayer and mencoder and found that lavcopts acodec no longer accepts the "aac" option. That is the one I use to encode video for the iPod. mencoder -ovc lavc -lavcopts vcodec=mpeg4:vbitrate=2500:vqmin=2:vqmax=10:acodec=aac:vglobal=1:aglobal=1:abitrate=128:aspect="4/3" -oac lavc -lavfopts format=mp4 -vf scale="320:240",harddup -of lavf -o /media/My\ Video/iPod/Tesgt.mp4 /media/My\ Video/Raw/Test.mpg MEncoder 1.0rc2-4.2.1 (C) 2000-2007 MPlayer Team CPU: Intel(R) Pentium(R) M processor 2.00GHz (Family: 6, Model: 13, Stepping: 8) CPUflags: Type: 6 MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 1 SSE2: 1 Compiled for x86 CPU with extensions: MMX MMX2 SSE SSE2 success: format: 0 data: 0x0 - 0xa05ad58 MPEG-PS file format detected. VIDEO: MPEG2 480x480 (aspect 2) 29.970 fps 5800.0 kbps (725.0 kbyte/s) [V] filefmt:2 fourcc:0x1002 size:480x480 fps:29.97 ftime:=0.0334 == Opening audio decoder: [mp3lib] MPEG layer-2, layer-3 AUDIO: 48000 Hz, 2 ch, s16le, 192.0 kbit/12.50% (ratio: 24000->192000) Selected audio codec: [mp3] afm: mp3lib (mp3lib MPEG layer-2, layer-3) == ** MUXER_LAVF * REMEMBER: MEncoder's libavformat muxing is presently broken and can generate INCORRECT files in the presence of B frames. Moreover, due to bugs MPlayer will play these INCORRECT files as if nothing were wrong! *** OK, exit Opening video filter: [expand osd=1] Expand: -1 x -1, -1 ; -1, osd: 1, aspect: 0.00, round: 1 Opening video filter: [harddup] Opening video filter: [scale w=320 h=240] == Opening video decoder: [mpegpes] MPEG 1/2 Video passthrough VDec: vo config request - 480 x 480 (preferred colorspace: Mpeg PES) The selected video_out device is incompatible with this codec. Try appending the scale filter to your filter list, e.g. -vf spp,scale instead of -vf spp. VDecoder init failed :( Opening video decoder: [libmpeg2] MPEG 1/2 Video decoder libmpeg2-v0.4.0b Selected video codec: [mpeg12] vfm: libmpeg2 (MPEG-1 or 2 (libmpeg2)) == Audio LAVC, couldn't find encoder for codec aac. 'acodec=aac' worked in the version now in ports, although that version failed to write the header with a floating point error. :-( -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 pgpN2JiqxKvGx.pgp Description: PGP signature
Re: Please test: mplayer 1.0 rc2
> Date: Thu, 8 Nov 2007 11:12:49 +0900 > From: "Thomas Zander" <[EMAIL PROTECTED]> > > On 07/11/2007, Kevin Oberman <[EMAIL PROTECTED]> wrote: > > > 'acodec=aac' worked in the version now in ports, although that version > > failed to write the header with a floating point error. :-( > > Does this mean it has never been in a really useful state? No. It was working fine back in August and before. I only started getting the floating point errors recently. I "lost" acodec=aac in rc2. Since I didn't try making any mp4s for my iPod after August, I can't say exactly when it stopped working, but there have not been many updates since then. (BTW, I get the floating point error with ffmpeg, too.) Here is the info for one that was created on Aug. 23. Playing MP4/Test.mp4. Quicktime/MOV file format detected. ID_VIDEO_ID=0 [mov] Video stream found, -vid 0 ID_AUDIO_ID=1 [mov] Audio stream found, -aid 1 VIDEO: [mp4v] 640x480 24bpp 29.970 fps0.0 kbps ( 0.0 kbyte/s) ID_FILENAME=MP4/Test.mp4 ID_DEMUXER=mov ID_VIDEO_FORMAT=mp4v ID_VIDEO_BITRATE=0 ID_VIDEO_WIDTH=640 ID_VIDEO_HEIGHT=480 ID_VIDEO_FPS=29.970 ID_VIDEO_ASPECT=0. ID_AUDIO_FORMAT=mp4a ID_AUDIO_BITRATE=0 ID_AUDIO_RATE=48000 ID_AUDIO_NCH=2 ID_LENGTH=199.80 == Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family Selected video codec: [ffodivx] vfm: ffmpeg (FFmpeg MPEG-4) == ID_VIDEO_CODEC=ffodivx == Opening audio decoder: [faad] AAC (MPEG2/4 Advanced Audio Coding) FAAD: compressed input bitrate missing, assuming 128kbit/s! AUDIO: 48000 Hz, 2 ch, s16le, 128.0 kbit/8.33% (ratio: 16000->192000) ID_AUDIO_BITRATE=128000 ID_AUDIO_RATE=48000 ID_AUDIO_NCH=2 Selected audio codec: [faad] afm: faad (FAAD AAC (MPEG-2/MPEG-4 Audio) decoder) == AO: [oss] 48000Hz 2ch s16le (2 bytes per sample) ID_AUDIO_CODEC=faad I usually update ports within a couple if days of entry into the ports tree, so the version Aug. 5 most likely worked. I will re-install it shortly. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 pgp46JsQzGCOC.pgp Description: PGP signature
Re: Please test: mplayer 1.0 rc2
> Date: Thu, 8 Nov 2007 11:12:49 +0900 > From: "Thomas Zander" <[EMAIL PROTECTED]> > > On 07/11/2007, Kevin Oberman <[EMAIL PROTECTED]> wrote: > > > 'acodec=aac' worked in the version now in ports, although that version > > failed to write the header with a floating point error. :-( > > Does this mean it has never been in a really useful state? > > Riggs > The problem prior to rc2 turned out to be a bad faac port. Now that I have rolled it back to 1.25, the current rc1 port works again. Unfortunately, rc2 still says that 'aac' is not a valid lavcodec option. I can encode with '-oac faac' which really should use the same code under the hood, but it still seems like something is broken in rc2. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 pgpkuQ4r2hzos.pgp Description: PGP signature
Re: Please test: mplayer 1.0 rc2
> Date: Wed, 7 Nov 2007 22:42:57 -0800 > From: "Kevin Downey" <[EMAIL PROTECTED]> > > On Nov 7, 2007 10:02 PM, Kevin Downey <[EMAIL PROTECTED]> wrote: > > > > On Nov 7, 2007 8:25 PM, Kevin Oberman <[EMAIL PROTECTED]> wrote: > > > > Date: Thu, 8 Nov 2007 11:12:49 +0900 > > > > From: "Thomas Zander" <[EMAIL PROTECTED]> > > > > > > > > On 07/11/2007, Kevin Oberman <[EMAIL PROTECTED]> wrote: > > > > > > > > > 'acodec=aac' worked in the version now in ports, although that version > > > > > failed to write the header with a floating point error. :-( > > > > > > > > Does this mean it has never been in a really useful state? > > > > > > No. It was working fine back in August and before. I only started > > > getting the floating point errors recently. I "lost" acodec=aac in > > > rc2. Since I didn't try making any mp4s for my iPod after August, I > > > can't say exactly when it stopped working, but there have not been many > > > updates since then. (BTW, I get the floating point error with ffmpeg, > > > too.) > > > > > > Here is the info for one that was created on Aug. 23. > > > Playing MP4/Test.mp4. > > > Quicktime/MOV file format detected. > > > ID_VIDEO_ID=0 > > > [mov] Video stream found, -vid 0 > > > ID_AUDIO_ID=1 > > > [mov] Audio stream found, -aid 1 > > > VIDEO: [mp4v] 640x480 24bpp 29.970 fps0.0 kbps ( 0.0 kbyte/s) > > > ID_FILENAME=MP4/Test.mp4 > > > ID_DEMUXER=mov > > > ID_VIDEO_FORMAT=mp4v > > > ID_VIDEO_BITRATE=0 > > > ID_VIDEO_WIDTH=640 > > > ID_VIDEO_HEIGHT=480 > > > ID_VIDEO_FPS=29.970 > > > ID_VIDEO_ASPECT=0. > > > ID_AUDIO_FORMAT=mp4a > > > ID_AUDIO_BITRATE=0 > > > ID_AUDIO_RATE=48000 > > > ID_AUDIO_NCH=2 > > > ID_LENGTH=199.80 > > > == > > > Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family > > > Selected video codec: [ffodivx] vfm: ffmpeg (FFmpeg MPEG-4) > > > == > > > ID_VIDEO_CODEC=ffodivx > > > == > > > Opening audio decoder: [faad] AAC (MPEG2/4 Advanced Audio Coding) > > > FAAD: compressed input bitrate missing, assuming 128kbit/s! > > > AUDIO: 48000 Hz, 2 ch, s16le, 128.0 kbit/8.33% (ratio: 16000->192000) > > > ID_AUDIO_BITRATE=128000 > > > ID_AUDIO_RATE=48000 > > > ID_AUDIO_NCH=2 > > > Selected audio codec: [faad] afm: faad (FAAD AAC (MPEG-2/MPEG-4 Audio) > > > decoder) > > > == > > > AO: [oss] 48000Hz 2ch s16le (2 bytes per sample) > > > ID_AUDIO_CODEC=faad > > > > > > I usually update ports within a couple if days of entry into the ports > > > tree, so the version Aug. 5 most likely worked. I will re-install it > > > shortly. > > > -- > > > R. Kevin Oberman, Network Engineer > > > Energy Sciences Network (ESnet) > > > Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) > > > E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 > > > Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 > > > > > > > it is possible to have -oac faac and bypass lavc > > > > mencoder -oac help|grep faac > >faac - FAAC AAC audio encoder > > > > but libfaac (/usr/ports/audio/faac) which every free encoder program > > seems to use (mencoder, ffmpeg, vlc) stopped creating valid streams > > for me sometime in the last month or two. Does not seem to be related. > > > > The current faac port is 1.26 and thats what gives me invalid aac > streams (won't play in quicktime or mplayer). the previous version > 1.25 does work and is usable with mencoder so you might try that > instead of -oac lavc -lavcopts acodec=faac > Thanks very much! I wonder if the mplayerhq folks have decided to pull faac from lavc since identical code is available using either lavc or faac. It is possible (likely) that the man pages are a bit behind the state of the RC code. In any case, I will modify my tools to use '-oac faac -faacopts ...' -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 pgpFYoro4U5q9.pgp Description: PGP signature
Re: Please test: mplayer 1.0 rc2
> Date: Wed, 7 Nov 2007 22:42:57 -0800 > From: "Kevin Downey" <[EMAIL PROTECTED]> > > On Nov 7, 2007 10:02 PM, Kevin Downey <[EMAIL PROTECTED]> wrote: > > > > On Nov 7, 2007 8:25 PM, Kevin Oberman <[EMAIL PROTECTED]> wrote: > > > > Date: Thu, 8 Nov 2007 11:12:49 +0900 > > > > From: "Thomas Zander" <[EMAIL PROTECTED]> > > > > > > > > On 07/11/2007, Kevin Oberman <[EMAIL PROTECTED]> wrote: > > > > > > > > > 'acodec=aac' worked in the version now in ports, although that version > > > > > failed to write the header with a floating point error. :-( > > > > > > > > Does this mean it has never been in a really useful state? > > > > > > No. It was working fine back in August and before. I only started > > > getting the floating point errors recently. I "lost" acodec=aac in > > > rc2. Since I didn't try making any mp4s for my iPod after August, I > > > can't say exactly when it stopped working, but there have not been many > > > updates since then. (BTW, I get the floating point error with ffmpeg, > > > too.) > > > > > > Here is the info for one that was created on Aug. 23. > > > Playing MP4/Test.mp4. > > > Quicktime/MOV file format detected. > > > ID_VIDEO_ID=0 > > > [mov] Video stream found, -vid 0 > > > ID_AUDIO_ID=1 > > > [mov] Audio stream found, -aid 1 > > > VIDEO: [mp4v] 640x480 24bpp 29.970 fps0.0 kbps ( 0.0 kbyte/s) > > > ID_FILENAME=MP4/Test.mp4 > > > ID_DEMUXER=mov > > > ID_VIDEO_FORMAT=mp4v > > > ID_VIDEO_BITRATE=0 > > > ID_VIDEO_WIDTH=640 > > > ID_VIDEO_HEIGHT=480 > > > ID_VIDEO_FPS=29.970 > > > ID_VIDEO_ASPECT=0. > > > ID_AUDIO_FORMAT=mp4a > > > ID_AUDIO_BITRATE=0 > > > ID_AUDIO_RATE=48000 > > > ID_AUDIO_NCH=2 > > > ID_LENGTH=199.80 > > > == > > > Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family > > > Selected video codec: [ffodivx] vfm: ffmpeg (FFmpeg MPEG-4) > > > == > > > ID_VIDEO_CODEC=ffodivx > > > == > > > Opening audio decoder: [faad] AAC (MPEG2/4 Advanced Audio Coding) > > > FAAD: compressed input bitrate missing, assuming 128kbit/s! > > > AUDIO: 48000 Hz, 2 ch, s16le, 128.0 kbit/8.33% (ratio: 16000->192000) > > > ID_AUDIO_BITRATE=128000 > > > ID_AUDIO_RATE=48000 > > > ID_AUDIO_NCH=2 > > > Selected audio codec: [faad] afm: faad (FAAD AAC (MPEG-2/MPEG-4 Audio) > > > decoder) > > > == > > > AO: [oss] 48000Hz 2ch s16le (2 bytes per sample) > > > ID_AUDIO_CODEC=faad > > > > > > I usually update ports within a couple if days of entry into the ports > > > tree, so the version Aug. 5 most likely worked. I will re-install it > > > shortly. > > > -- > > > R. Kevin Oberman, Network Engineer > > > Energy Sciences Network (ESnet) > > > Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) > > > E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 > > > Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 > > > > > > > it is possible to have -oac faac and bypass lavc > > > > mencoder -oac help|grep faac > >faac - FAAC AAC audio encoder > > > > but libfaac (/usr/ports/audio/faac) which every free encoder program > > seems to use (mencoder, ffmpeg, vlc) stopped creating valid streams > > for me sometime in the last month or two. Does not seem to be related. > > > > The current faac port is 1.26 and thats what gives me invalid aac > streams (won't play in quicktime or mplayer). the previous version > 1.25 does work and is usable with mencoder so you might try that > instead of -oac lavc -lavcopts acodec=faac > Thanks! I just re-built faac 1.25 and acodec=aac works again, at least for the version in ports. I'll have to re-build rc2 and see if it is any different, but I don't imagine that it will be since it simply said that it didn't recognize the aac argument for acodec. Thanks again! -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 pgpUtno6Ak61q.pgp Description: PGP signature
xmms fails to play on 7.0
I have two FreeBSD systems running 7.0 and xmms fails to play MP3s on both systems. It starts up, but when I play, the time zips through the MP3 at around 100 times the correct speed. (About 3.25 seconds for a 4 minute MP3). The spectrum display seems to show the song playing, but there is no sound. I do get the error: Gtk-WARNING **: Failed to load module "libgnomebreakpad.so": Shared object "libgnomebreakpad.so" not found, required by "xmms" I get this with a lot of working Gnome apps, so I suspect it is a read herring. I can confirm that I have /usr/local/lib/gtk-2.0/modules/libgnomebreakpad.so, but I am not sure if that directory is in the shared library load path. Other players including totem and mpg123 play it fine, so it is specific to xmms. Any ideas? Shall I fine a PR? -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 pgpD7dwFfN8I6.pgp Description: PGP signature
Re: xmms fails to play on 7.0
> From: Beech Rintoul <[EMAIL PROTECTED]> > Date: Thu, 28 Feb 2008 21:03:10 -0900 > > On Thursday 28 February 2008, Kevin Oberman said: > > I have two FreeBSD systems running 7.0 and xmms fails to play MP3s > > on both systems. It starts up, but when I play, the time zips > > through the MP3 at around 100 times the correct speed. (About 3.25 > > seconds for a 4 minute MP3). The spectrum display seems to show the > > song playing, but there is no sound. > > > > I do get the error: > > Gtk-WARNING **: Failed to load module "libgnomebreakpad.so": Shared > > object "libgnomebreakpad.so" not found, required by "xmms" > > > > I get this with a lot of working Gnome apps, so I suspect it is a > > read herring. I can confirm that I have > > /usr/local/lib/gtk-2.0/modules/libgnomebreakpad.so, but I am not > > sure if that directory is in the shared library load path. > > > > Other players including totem and mpg123 play it fine, so it is > > specific to xmms. > > > > Any ideas? Shall I fine a PR? > > Check that your output plugin is set to OSS and not the Disk Writer > plugin in your preferences. What your describing sounds exactly like > the behavior when you're converting something to burn. If that's not > it, file a pr with as much config and system info as you can. Also, > you didn't say if you were running xmms or xmms2. Jackpot!!! Thanks so much, Beech. I have no idea why the last upgrade of xmms caused the default to switch output devices, but it did on all 3 of my systems and switching back to OSS fixed it right up. That said, I still plan to move to xmms2 after my system finishes rebuilding all of its ports this weekend after my move from RELENG_7 to HEAD. (I normally run HEAD, but I stay on a new version until it is released.) Thanks again! -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 pgpt13RNISTrv.pgp Description: PGP signature
Re: FreeBSD Port: xorg-7.3_1
> Date: Thu, 6 Mar 2008 20:45:22 +0100 > From: "Laurent Grangeau" <[EMAIL PROTECTED]> > Sender: [EMAIL PROTECTED] > > Hi there ! > > I've been using FreeBSD now for 4 months and it's a great OS. But is there a > way to install minimal Xorg server without installing the meta-port (and > thus, without all of the drivers) ? > > I'm using portinstall as the installer and I've been able to install > completely xorg-xserver and nvidia-driver until now, but I'm not able tu > launch the "startx" script. Where is that damned script (I mean, in which > package) ? > > I'm running minimal install of FreeBSD 7.0. Sure. Just cd /usr/ports/x11-drivers make config Select the drivers you want (and deselect those you don't want) That is it. The options are "sticky and should remain unchanged unless you 'make rmconfig' or a port update changes them. As for startx, # pkg_info -W /usr/local/bin/startx /usr/local/bin/startx was installed by package xinit-1.0.7 -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 pgpSCnkLGVG8H.pgp Description: PGP signature
Weird problems with portupgrade
I have been having strange problems with portupgrade on one RELENG_7 system for the past couple of months. The problem is that, when a port is built successfully, the upgrade of ports dependent on that port will fail to build because portupgrade thinks that the build of the dependency failed. -- Installing ./html/right.png -- Installing ./html/style.css -- Installing ./html/up.png -- Installing ./html/index.sgml gmake[3]: Leaving directory `/usr/ports/www/epiphany/work/epiphany-2.22.1.1/doc/reference' gmake[2]: Leaving directory `/usr/ports/www/epiphany/work/epiphany-2.22.1.1/doc/reference' gmake[2]: Entering directory `/usr/ports/www/epiphany/work/epiphany-2.22.1.1/doc' gmake[3]: Entering directory `/usr/ports/www/epiphany/work/epiphany-2.22.1.1/doc' gmake[3]: Nothing to be done for `install-exec-am'. test -z "/usr/local/man/man1" || /usr/local/bin/gmkdir -p "/usr/local/man/man1" install -o root -g wheel -m 444 './epiphany.1' '/usr/local/man/man1/epiphany.1' gmake[3]: Leaving directory `/usr/ports/www/epiphany/work/epiphany-2.22.1.1/doc' gmake[2]: Leaving directory `/usr/ports/www/epiphany/work/epiphany-2.22.1.1/doc' gmake[1]: Leaving directory `/usr/ports/www/epiphany/work/epiphany-2.22.1.1/doc' gmake[1]: Entering directory `/usr/ports/www/epiphany/work/epiphany-2.22.1.1' gmake[2]: Entering directory `/usr/ports/www/epiphany/work/epiphany-2.22.1.1' gmake[2]: Nothing to be done for `install-exec-am'. gmake[2]: Nothing to be done for `install-data-am'. gmake[2]: Leaving directory `/usr/ports/www/epiphany/work/epiphany-2.22.1.1' gmake[1]: Leaving directory `/usr/ports/www/epiphany/work/epiphany-2.22.1.1' install -o root -g wheel -m 444 /usr/ports/www/epiphany/work/epiphany-2.22.1.1/data/epiphany-fonts.schemas /usr/local/etc/gconf/schemas ===> Compressing manual pages for epiphany-2.22.1.1 ===> Running ldconfig /sbin/ldconfig -m /usr/local/lib ===> Registering installation for epiphany-2.22.1.1 pkg_create: dependency loop detected for package gnome-desktop-2.22.1 pkg_create: dependency loop detected for package gnome-desktop-2.22.1 ===> Cleaning for epiphany-2.22.1.1 ---> Cleaning out obsolete shared libraries [Updating the pkgdb in /var/db/pkg ... - 1007 packages found (-0 +1) . done] ---> Skipping 'www/epiphany-extensions' (epiphany-extensions-2.22.0) because a requisite package 'epiphany-2.22.0_1' () failed (specify -k to force) ---> Upgrading 'yelp-2.22.0' to 'yelp-2.22.1' (x11/yelp) I have re-build pkgdb and portsdb, though I can't see why these would cause this. I have also re-installed both ruby and portupgrade. I just run portupgrade -a" until everything gets built, but it is really annoying. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 pgphEiZgoUzcL.pgp Description: PGP signature
Re: what is gio-fam?
> From: Mikhail Teterin <[EMAIL PROTECTED]> > Date: Mon, 14 Apr 2008 16:18:56 -0400 > Sender: [EMAIL PROTECTED] > > понедÑлок 14 квÑÑÐµÐ½Ñ 2008 03:52 по, Dominic Fandrey Ðи > напиÑали: > > > So, once again, I have to update half of my ports in order to add a new > > > port to the system, that's happily functioning with the older version(s). > > > > Or you install sysutils/bsdadminscripts and run pkg_libchk to see which > > ports actually require rebuilding. > > NONE of them /require/ rebuilding, if I'm happy with the existing version. > Yet, I'm being forced to rebuild them so that I can add another piece of > software (which is also happy with the versions I already have) -- and I > don't like that at all... If the port existed in a version prior to the release of 2.22 (see /usr/ports/UPDATING for the date), grab the port from just before that date. if your use csup or cvsup, you can do this by editing your supfile to include a date and run csup/cvsup with the -i option. It's really is not that hard, although it is a bit of work. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 pgpfY3zE52Mda.pgp Description: PGP signature
cvsup4 seems to be badly constipated
Don't know if this is the appropriate place for this report, but cvsup4 seems to be permanently saying that too many users are logged in and to try again later. Been that wat for about a day. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 pgpKFjhhRWzHQ.pgp Description: PGP signature
Re: cvsup4 seems to be badly constipated
> From: Chuck Swiger <[EMAIL PROTECTED]> > Date: Fri, 18 Apr 2008 15:23:22 -0700 > > On Apr 18, 2008, at 2:46 PM, Kevin Oberman wrote: > > Don't know if this is the appropriate place for this report, but > > cvsup4 > > seems to be permanently saying that too many users are logged in and > > to > > try again later. Been that wat for about a day. > > Seems to be working fine, here: > > -- > >>> Running /usr/local/bin/cvsup > -- > Connected to cvsup4.FreeBSD.org > Updating collection src-all/cvs > Edit src/contrib/gcc/config/i386/freebsd64.h > [ ... ] > How odd. I still see only: ptavv# csup -L2 /root/ports-supfile Parsing supfile "/root/ports-supfile" Connecting to cvsup4.freebsd.org Cannot connect to 2001:4f8:0:2::e: Connection refused Connected to 204.152.184.73 Rejected by server: Access limit exceeded; try again later Will retry at 16:27:34 I get the same from a large number of systems. I moved to use cvsup2 and it works fine. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 pgpSMmvZUrWI1.pgp Description: PGP signature
Re: textproc/p5-XML-SAX: prerequisite XML::SAX::Base 1.05 not found
al/lib/perl5/site_perl/5.14.2/XML/SAX/PurePerl/DocType.pm >> Installing >> /usr/local/lib/perl5/site_perl/5.14.2/XML/SAX/PurePerl/EncodingDetect.pm >> Installing >> /usr/local/lib/perl5/site_perl/5.14.2/XML/SAX/PurePerl/DebugHandler.pm >> Installing >> /usr/local/lib/perl5/site_perl/5.14.2/XML/SAX/PurePerl/Productions.pm >> Installing /usr/local/lib/perl5/site_perl/5.14.2/XML/SAX/PurePerl/XMLDecl.pm >> Installing /usr/local/lib/perl5/site_perl/5.14.2/XML/SAX/PurePerl/DTDDecls.pm >> Installing /usr/local/lib/perl5/site_perl/5.14.2/XML/SAX/PurePerl/Reader.pm >> Installing >> /usr/local/lib/perl5/site_perl/5.14.2/XML/SAX/PurePerl/Reader/UnicodeExt.pm >> Installing >> /usr/local/lib/perl5/site_perl/5.14.2/XML/SAX/PurePerl/Reader/Stream.pm >> Installing >> /usr/local/lib/perl5/site_perl/5.14.2/XML/SAX/PurePerl/Reader/NoUnicodeExt.pm >> Installing >> /usr/local/lib/perl5/site_perl/5.14.2/XML/SAX/PurePerl/Reader/String.pm >> Installing >> /usr/local/lib/perl5/site_perl/5.14.2/XML/SAX/PurePerl/Reader/URI.pm >> Can't locate XML/SAX/Exception.pm in @INC (@INC contains: >> /usr/local/lib/perl5/5.14.2/BSDPAN /usr/local/lib/perl5/site_perl/5.14.2/mach >> /usr/local/lib/perl5/site_perl/5.14.2 /usr/local/lib/perl5/5.14.2/mach >> /usr/local/lib/perl5/5.14.2 .) at >> /usr/local/lib/perl5/site_perl/5.14.2/XML/SAX/ParserFactory.pm line 12. >> BEGIN failed--compilation aborted at >> /usr/local/lib/perl5/site_perl/5.14.2/XML/SAX/ParserFactory.pm line 12. >> Compilation failed in require at >> /usr/local/lib/perl5/site_perl/5.14.2/XML/SAX.pm line 18. >> BEGIN failed--compilation aborted at >> /usr/local/lib/perl5/site_perl/5.14.2/XML/SAX.pm line 18. >> Compilation failed in require. >> BEGIN failed--compilation aborted. >> *** [install_sax_pureperl] Error code 2 >> Stop in /usr/ports/textproc/p5-XML-SAX/work/XML-SAX-0.99. >> *** [do-install] Error code 1 >> Stop in /usr/ports/textproc/p5-XML-SAX. >> ===>>> A backup package for p5-XML-SAX-0.96 should >> be located in /usr/ports/packages/portmaster-backup >> ===>>> Installation of p5-XML-SAX-0.99 (textproc/p5-XML-SAX) failed >> ===>>> Aborting update >> Terminated >> ===>>> You can restart from the point of failure with this command line: >> portmaster textproc/p5-XML-SAX >> >> >> It seems that ParserFactory.pm (line 12) wants to use XML::SAX::Exception, >> but >> there is no ParserDetails anymore (just deleted before ...). >> >> This happens on several boxes with recent 10.0-CURRENT (amd64). Does anyone >> else >> see this behaviour? >> >> Any help is appreciated. > > I think that p5-XML-SAX-Base has to be removed before installing (maybe even > building) p5-XML-SAX-0.99. I did a "pkg_delete p5-XML-SAX-Base-\*" followed by "portmaster p5-XML-SAX-Base" and "portmaster p5-XML-SAX". Once I did that, everything went fine. (In theaory I could have deleted p5-XML-SAX-Base and then installed both p5-XML-SAX-Base and p5-XML-SAX in a single portmaster run, but I didn't do it that way, so I can't promise that it will work. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: textproc/p5-XML-SAX: prerequisite XML::SAX::Base 1.05 not found
On Wed, May 9, 2012 at 6:02 PM, Adam McDougall wrote: > On 5/9/2012 6:36 PM, milki wrote: >> >> On 09:26 Wed 09 May , Kevin Oberman wrote: >>>> >>>> I think that p5-XML-SAX-Base has to be removed before installing (maybe >>>> even >>>> building) ?p5-XML-SAX-0.99. >>> >>> I did a "pkg_delete p5-XML-SAX-Base-\*" followed by "portmaster >>> p5-XML-SAX-Base" and "portmaster p5-XML-SAX". Once I did that, >>> everything went fine. (In theaory I could have deleted >>> p5-XML-SAX-Base and then installed both p5-XML-SAX-Base and p5-XML-SAX >>> in a single portmaster run, but I didn't do it that way, so I can't >>> promise that it will work. >> >> Do either of you remember how p5-XML-SAX-Base was installed? The port >> was removed 6 years ago and sunpoet readded it with the 0.99 update. It >> appears to have already been installed according to your port logs but >> not detected by the perl install itself, which means it there is some >> discrepency in the package's file locations. >> >> -milki >> > I ran into this problem today from some servers I installed 2 days ago. I > did not have p5-XML-SAX-Base-1.08 installed prior to running portupgrade -a > this morning which installed it then p5-XML-Sax failed. If I remove > p5-XML-SAX-Base-1.08 and let portupgrade re-add whatever it wants, it > worked. p5-XML-SAX-Base was installed before re-installing p5-XML-Sax, which would have installed the required file but reinstalling don't recall exactly what order it was installing them in, unfortunately. I thought it installed Base first, but it would have done so before XML-SAX deleted the file when deleting the old p5-XML-SAX. Remember, it was in the packing list for the old version. Now that the damage was done, re-installing Base restored the missing file and p5-XML-SAX no longer tried to delete it. No real reason to de-install Base. Simply re-installing it would have done the job. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: textproc/p5-XML-SAX: prerequisite XML::SAX::Base 1.05 not found
On Sat, May 12, 2012 at 5:08 AM, Heino Tiedemann wrote: > Heino Tiedemann wrote: > >> Andriy Gapon wrote: >> >>>> >>>> Any help is appreciated. >>> >>> I think that p5-XML-SAX-Base has to be removed before installing (maybe even >>> building) p5-XML-SAX-0.99. >> >> does not work. :( > > it woks with > > cd /usr/ports/textproc/p5-XML-SAX > make deinstall > cd ../p5-XML-SAX-Base > make deinstall > make > make install > cd ../p5-XML-SAX > make install > > > No idea why, but portupgrade und pkg_deinstall was not he right way... > > thanks to Kurt! The Exception.pm file was moved from p5-XML-SAX to the new p5-XML-SAX-Base port. Since p5-XML-SAX-Base is a dependency of p5-XML-SAX, it gets installed first and it installs Exception.pm over the existing copy that was previously installed by p5-XML-SAX. Then it updates p5-XML-SAX and, since p5-XML-SAX has Exception.pm in its pkg_plist, it deletes the file.Note that the error is during the 'install' operation, not the 'build'. The 'right' answer that there should have been a note in UPDATING that warns that you need to: pkg_delete p5-XML-SAX-0\* portmaster textproc/p5-XML-SAX-Base textproc/p5-XML-SAX (with similar command for portupgrade). -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Please test geodns.portsnap.freebsd.org
On Sat, May 12, 2012 at 8:58 AM, Leslie Jensen wrote: > > > 2012-05-12 16:19, RW skrev: > >> On Sat, 12 May 2012 14:16:58 +0200 >> Leslie Jensen wrote: >> >>> >>> >>> 2012-05-12 12:34, Colin Percival skrev: >>>> >>>> On 05/12/12 00:22, Leslie Jensen wrote: >>>>> >>>>> host -t srv _http._tcp.geodns.portsnap.freebsd.org >>>>> ;; Truncated, retrying in TCP mode. >>>>> ;; Connection to 172.17.0.1#53(172.17.0.1) for >>>>> _http._tcp.geodns.portsnap.freebsd.org failed: connection refused. >>>> >>>> >>>> Ok, you have a broken recursive DNS server configuration. >>>> >>>> I'll have A records as a fallback for situations like this where >>>> SRV can't be used. >>>> >>> >>> What exactly does that mean? The IP-address is my home router that >>> acts as a caching DNS for my network. The router in turn uses my >>> ISP's DNS. >>> >>> So if there is a configuration issue I'll be willing to drop a letter >>> to my ISP in order to get it fixed. >> >> >> Probably your router doesn't support SRV records, try putting external >> servers in resolv.conf. >> ___ >> freebsd-ports@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-ports >> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > > > > Well I had to read up on configuring dhclient.conf > > After adding > > prepend domain-name-servers y.y.y.y, x.x.x.x; > > To my /etc/dhclient.conf > > I now get the following and it looks to me as it works :-) > > > > host -t srv _http._tcp.geodns.portsnap.freebsd.org > ;; Truncated, retrying in TCP mode. > _http._tcp.geodns.portsnap.freebsd.org has SRV record 4 10 80 > ap-southeast-1.portsnap.freebsd.org. > _http._tcp.geodns.portsnap.freebsd.org has SRV record 1 10 80 > geodns-1.portsnap.freebsd.org. > _http._tcp.geodns.portsnap.freebsd.org has SRV record 2 10 80 > geodns-2.portsnap.freebsd.org. > _http._tcp.geodns.portsnap.freebsd.org has SRV record 3 10 80 > geodns-3.portsnap.freebsd.org. > _http._tcp.geodns.portsnap.freebsd.org has SRV record 4 10 80 > isc.portsnap.freebsd.org. > _http._tcp.geodns.portsnap.freebsd.org has SRV record 4 10 80 > your-org.portsnap.freebsd.org. > _http._tcp.geodns.portsnap.freebsd.org has SRV record 4 10 80 > ec2-eu-west-1.portsnap.freebsd.org. > _http._tcp.geodns.portsnap.freebsd.org has SRV record 4 10 80 > ec2-sa-east-1.portsnap.freebsd.org. > _http._tcp.geodns.portsnap.freebsd.org has SRV record 4 10 80 > ap-northeast-1.portsnap.freebsd.org. Warning! You will have more problems down the road. The real issue is that a firewall (or router ACL) is blocking port 53/tcp. This is distressingly common and will result in DNS issues more and more often. By default, DNS attempts to use UDP (53/udp) for DNS lookups. If the response is too big to fit into a UDP packet, the operation will fall back to using TCP, but many sites follow bad advice of blocking 53/tcp, so the lookup fails. This has been a growing problem as DNS responses are getting longer due to things like this, IPv6, and DNSSEC. Please contact whoever is responsible for your router/firewall and ask that 53/tcp be allowed. Otherwise, more and more things will break. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Evince fails upgrade
On Wed, May 23, 2012 at 7:34 AM, Robert wrote: > > Hello Port readers > > I am unable to upgrade to latest evince due to following failure. > Evince now calls for www/yelp which calls for www/libxul which has > vulnerabilities. > > [robert@dell64] /usr/ports/x11/yelp% sudo make install clean > > yelp is using libxul for gecko support, but you can > change that by defining WITH_GECKO to the following values: > > libxul > > ===> License check disabled, port has not defined LICENSE > ===> Extracting for yelp-2.30.2_2 > => SHA256 Checksum OK for gnome2/yelp-2.30.2.tar.bz2. > /bin/rm -f /usr/ports/x11/yelp/work/yelp-2.30.2/data/yelp.schemas > ===> Patching for yelp-2.30.2_2 > ===> Applying FreeBSD patches for yelp-2.30.2_2 > ===> yelp-2.30.2_2 depends on file: /usr/local/lib/libxul/libxul.so - > not found ===> Verifying install for /usr/local/lib/libxul/libxul.so > in /usr/ports/www/libxul ===> libxul-1.9.2.28 has known > vulnerabilities: Affected package: libxul-1.9.2.28 > Type of problem: mozilla -- multiple vulnerabilities. > Reference: > http://portaudit.FreeBSD.org/380e8c56-8e32-11e1-9580-4061862b8c22.html > => Please update your ports tree and try again. *** Error code 1 > > Stop in /usr/ports/www/libxul. > *** Error code 1 > > Stop in /usr/ports/www/libxul. > *** Error code 1 > > Stop in /usr/ports/x11/yelp. > > I have tried to comment out the WITH_GECKO line but that fails also. > The Makefile already has > > WITH_GECKO= libxul > > What do I need to change it to? There is nothing to change it to, as far as I know. There used to other options, but libxul is the only one left. Unfortunately, it has a vulnerability, so won't build. You can either force it by setting DISABLE_VULNERABILITIES and live with the vulnerability or wait until libxul is fixed, assuming that it is. Other ports that use GECKO have the same problem. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: KDE 4.8
On Fri, May 25, 2012 at 2:54 PM, ajtiM wrote: > I use portmaster for KDE 4.8 updtae and it stopped: > > The devel/kdebindings4-python port has been deleted: kdebindings ports have > been refactored. > > What do I need to do, please? Read /usr/ports/UPDATING and follow the instructions. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: lame-3.99.5
On Mon, May 28, 2012 at 9:12 PM, Shiva Subramanian wrote: > hi there - when trying to install lame on my fresh new freebsd - I get the > following error msg. Anything I can do to help resolve? > > murugan02# pkg_add -r lame > Error: Unable to get > ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9.0-release/Latest/lame.tbz: > File unavailable (e.g., file not found, no access) > pkg_add: unable to fetch ' > ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9.0-release/Latest/lame.tbz' > by URL I don't believe that lame is ever packaged for legal reasons. You will need to build it yourself, if you want it. Binary distribution would require FreeBSD to license it (clearly a non-starter), so there is none. lame is not unique in this regard. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Options name, descriptions and consistency
On Tue, May 29, 2012 at 11:33 PM, Baptiste Daroussin wrote: > Hi all, > > On of the reasons of bsd.options.desc.mk is to be able to share common options > and descriptions, to have better consistency between ports and to have general > meaning descriptions that make more sense, has anyone can improve the > description of an option. > > about consistency, I can already see that some options are set in double just > with different name, one of our goal now should be to avoid it is not > necessary > and have the option name that make more sense. If I have a look at it now, > what > I can see is: > AAC_DESC?= Enable support for aac/mp4 > MP4_DESC?= Enable support for mp4 Hmm. I don't understand why one should assume that aac should pull in mp4 or the other way around. I may want to generate plain AAC (m4a) audio files with no mp4 use and I may want to generate an mp4 file using a codec other than AAC. The standard support several codecs, though AAC is clearly dominant and I suspect is universal in commercial DVDs. But I have many mp4s with (yuck) MP2 audio as is generated by my HD component video to computer interface. It's going to be really hard to deal with these sorts of things. But being able to set for IPv6 support once instead of per port would be very nice. I also suspect that multimedia is a particularly ugly case for this sort of thing. > > Both added by me :) > > In this particular case, I think only one is useful > same goes for; > > ID3TAG_DESC?= Support ID3 v1/v2 tags > ID3_DESC?= Enable support for id3 tags Here I think you are right. I can't imagine a case where they are not, though my imagination might be lacking a bit. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Options name, descriptions and consistency
On Wed, May 30, 2012 at 1:46 PM, Alberto Villa wrote: > On Wed, May 30, 2012 at 8:33 AM, Baptiste Daroussin wrote: >> On of the reasons of bsd.options.desc.mk is to be able to share common >> options >> and descriptions, to have better consistency between ports and to have >> general >> meaning descriptions that make more sense, has anyone can improve the >> description of an option. > > While I really like what bsd.options.desc.mk is supposed to do, I > would like to recommend to any committer/maintainer (and I will > personally submit a patch for the soon-to-come documentation and for > the file itself) to think before always relying on on default option > descriptions. > > Sometimes just saying "Enable XXX support" doesn't mean anything to > the user, and a more explanatory text would be far better, explaining > maybe what feature one is about to enable instead of just what he is > going to depend on. > > So, please, do not hesitate to redefine option descriptions for your > ports if you feel you can add more information for the port specific > case. +1 Ports in multimedia are a perfect example of this problem. Many ports have dozens of options. While some (like enabling codecs of muxers) are either obvious or easy to ind out about in Wikipedia or by googling, others can be quite obscure. The short line in options really is little or no help for "Enable VPFRE support". Even in simpler ports, it is hard to know the effect of selecting an option in the particular case of port, especially when it is sometimes not obvious what an option has to do with a port. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [HEADSUP] New framework options aka optionng
On Wed, May 30, 2012 at 2:23 PM, Doug Barton wrote: > On 5/30/2012 3:33 AM, Vitaly Magerya wrote: >> Folks, when moving forward with optionsng, do we want to convert >> NOPORTDOCS and NOPORTEXAMPLES to options everywhere? > > Absolutely not. By far the majority of users benefit from installing the > docs and examples. Users who don't want them can continue to do what > they've always done, configure it in make.conf. Adding OPTIONS for these > would only cause confusion. I'll go one further and suggest that the vast majority who don't want these features are building specialized systems and they know very well what they are doing. A global setting for these would be desirable, though, as someone building a specialized distribution for, say, an embedded system, will want no docs or examples for any port. I suspect it is ALMOST always an all or nothing issue, not per port. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Please rebuild all ports that depend on PNG
On Sat, Jun 2, 2012 at 6:07 PM, Jerry wrote: > On Sat, 2 Jun 2012 17:34:59 +0100 > Chris Rees articulated: > >>On Jun 2, 2012 5:27 PM, "Jerry" wrote: >>> >>> On Sat, 2 Jun 2012 11:07:28 -0400 >>> b. f. articulated: >>> >>> >> > Realy no other possibility?! >>> >> >>> >> You need to rebuild all the ports that install binaries that link >>> >> against libpngNN.so.NN. That is actually a subset of the ports >>> >> that depend on graphics/png -- unfortunately it takes some effort >>> >> to identify precisely what does need rebuilding. There is the >>> >> pkg_libchk script (which is part of sysutils/bsdadminscripts) that >>> >> can help. >>> >... >>> >> Use pkg_libchk to prioritise the ports that really need to be >>> >> rebuilt. >>> > >>> >Lawrence Stewart's convenient script can be used with portmaster to >>> >perform this kind of update: >>> > >>> >https://lauren.room52.net/hg/scripts/raw-file/tip/libdepend/libdepend.sh >>> >>> I am receiving a: "This Connection is Untrusted" warning from Firefox >>> when I attempt to connect to that URL. It is probably harmless; >>> however, it certainly doesn't instill confidence is someone viewing >>> the site for the first time. >>> >> >>It just means he hasn't bought a certificate- no less trustworthy than >>vanilla (non-SSL) http. > > IMHO, if you are going to use "https" then you should have a proper SSL > certificate. A self-signed one means virtually nothing. If the web site > operator is not going to purchase an authentic certificate they why > use SSL at all? Just my 2¢ on the matter. No, it means that the transfer is encrypted. There is no guarantee that the site you are downloading from is the site you thought you were, but many people like to do https as a matter of principle. For this, self-signed certs are fine. And, if you think think a valid cert really guarantees anything other than encryption, you have not been paying attention to the news. There are lots of bogus, but properly signed certs out there. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: make failed for editors/libreoffice
On Fri, Jun 1, 2012 at 12:02 AM, Sergio de Almeida Lenzi
wrote:
> Em Qui, 2012-05-31 às 17:31 +0200, Leslie Jensen escreveu:
>
>>
>> 2012-05-31 14:24, Robert Huff skrev:
>> >
>> > Leslie Jensen writes:
>> >
>> >> ---
>> >> Oh dear - something failed during the build - sorry !
>> >> For more help with debugging build errors, please see the section in:
>> >> http://wiki.documentfoundation.org/Development
>> >>
>> >> internal build errors:
>> >>
>> >> ERROR: error 65280 occurred while making
>> >> /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/vcl/prj
>> >>
>> >> it seems that the error is inside 'vcl', please re-run build
>> >> inside this module to isolate the error and/or test your fix:
>> >> ---
>> >>
>> >> /usr/local/bin/bash
>> >> cd /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2
>> >> source ./Env.Host.sh
>> >> cd vcl
>> >> gmake clean # optional
>> >> gmake -r
>> >>
>> >> when the problem is isolated and fixed exit and re-run 'make' from the
>> >> top-level
>> >
>> >
>> > Did you follow the instructions?
>> >
>> >
>> > Robert Huff
>> >
>> > ___
>> > freebsd-ports@freebsd.org mailing list
>> > http://lists.freebsd.org/mailman/listinfo/freebsd-ports
>> > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>>
>>
>>
>> After four manual procedures I'm getting stuck here.
>>
>> What can I do?
>>
>> --
>> [ build MOD ] writerperfect
>> Bus error (core dumped)
>> File tested,Test Result,Execution Time (ms)
>> file:///usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/lotuswordpro/qa/cppunit/data/pass/A14.lwp,Signal
>> 11 during cups initialization called, ignoring cups
>>
>> Error: a unit test failed, please do one of:
>>
>> export DEBUGCPPUNIT=TRUE # for exception catching
>> export GDBCPPUNITTRACE="gdb --args" # for interactive debugging
>> export VALGRIND=memcheck # for memory checking
>> and retry.
>> gmake[1]: ***
>> [/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/workdir/unxfbsd.pro/CppunitTest/lotuswordpro_test_lotuswordpro.test]
>> Error 1
>> gmake[1]: *** Inväntar oavslutade jobb...
>> TEMPFILE=/tmp/gbuild.XX.gNM6YJsj && mv ${TEMPFILE}
>> /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/workdir/unxfbsd.pro/LinkTarget/Library/writerfilter_uno.uno.so.objectlist
>> gmake[1]: Lämnar katalogen
>> "/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/tail_build"
>> gmake: *** [source-env-and-recurse] Error 2
>>
>>
>> ___
>> freebsd-ports@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
>> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
> there is an error in the lotuswordpro testing... if you are not going
> to use lotuswrordpro
> apply these patch at the
> /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2
>
> ==
> --- lotuswordpro/Module_lotuswordpro.mk.orig 2012-05-31
> 19:34:52.014043605 -0300
> +++ lotuswordpro/Module_lotuswordpro.mk 2012-05-31 19:29:29.276164732
> -0300
> @@ -31,8 +31,8 @@
> Library_lwpft \
> ))
>
> -$(eval $(call gb_Module_add_check_targets,lotuswordpro,\
> - CppunitTest_lotuswordpro_test_lotuswordpro \
> -))
> +#$(eval $(call gb_Module_add_check_targets,lotuswordpro,\
> +# CppunitTest_lotuswordpro_test_lotuswordpro \
> +#))
>
> # vim: set noet sw=4 ts=4:
> =
I hit the same problem, applied the suggested patch and tried gmake
(in lotuswordpro) again.
/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/solenv/gbuild/Library.mk:54:
*** gb_Deliver_deliver: file does not exist in solver, and cannot be
delivered:
/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/solver/unxfbsd.pro/lib/libsfxlo.so.
Stop.
gmake[1]: *** Waiti
Re: portmaster -r png- Stop in /usr/ports/devel/gobject-introspection
On Sat, Jun 2, 2012 at 11:03 AM, Leslie Jensen wrote:
> Hello
>
>
> I can see that there's a problem with finding libpng.so.6
>
> I have
> /usr/local/lib/libpng15.so
> /usr/local/lib/libpng15.so.15
> /usr/local/lib/libpng.so
>
>
> I could make a soft link to one of the above and call it
> libpng.so.6.
>
> Is that a good way to solve this?
>
> Suggestions appreciated
>
>
> ---
> xtension__ ({ register __uint32_t __X = (_x); __asm ("bswap %0" : "+r"
> (__X)); __X; }));' at '{'
> /usr/include/machine/endian.h:130: syntax error, unexpected ';' in ' return
> (__extension__ ({ register __uint32_t __X = (_x); __asm ("bswap %0" : "+r"
> (__X)); __X; }));' at ';'
> /usr/bin/ld: warning: libpng.so.6, needed by /usr/local/lib/libcairo.so, not
> found (try using -rpath or -rpath-link)
> /libexec/ld-elf.so.1: Shared object "libpng.so.6" not found, required by
> "libcairo.so.2"
> Command
> '['/usr/ports/devel/gobject-introspection/work/gobject-introspection-0.10.8/tests/scanner/tmp-introspectyVPLgw/Regress-1.0',
> '--introspect-dump=/usr/ports/devel/gobject-introspection/work/gobject-introspection-0.10.8/tests/scanner/tmp-introspectyVPLgw/types.txt,/usr/ports/devel/gobject-introspection/work/gobject-introspection-0.10.8/tests/scanner/tmp-introspectyVPLgw/dump.xml']'
> returned non-zero exit status 1
> gmake[4]: *** [Regress-1.0.gir] Fel 1
> gmake[4]: Lämnar katalogen
> "/usr/ports/devel/gobject-introspection/work/gobject-introspection-0.10.8/tests/scanner"
> gmake[3]: *** [all-recursive] Fel 1
> gmake[3]: Lämnar katalogen
> "/usr/ports/devel/gobject-introspection/work/gobject-introspection-0.10.8/tests"
> gmake[2]: *** [all] Fel 2
> gmake[2]: Lämnar katalogen
> "/usr/ports/devel/gobject-introspection/work/gobject-introspection-0.10.8/tests"
> gmake[1]: *** [all-recursive] Fel 1
> gmake[1]: Lämnar katalogen
> "/usr/ports/devel/gobject-introspection/work/gobject-introspection-0.10.8"
> gmake: *** [all] Fel 2
> *** Error code 1
According to the message, libcairo.so.s is linked to libpng.so.6 which
is now obsolete. Looks like cairo has not been rebuilt for some
reason. Do you have /var/db/pkg/cairo-*/+IGNOREME? The problem with
cairo 1.10.2 appears to now be fixed, so you should be able to upgrade
it if that is why it did not get updated.
--
R. Kevin Oberman, Network Engineer
E-mail: kob6...@gmail.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Shared object "libpng.so.6"
On Sun, Jun 3, 2012 at 7:23 AM, b. f. wrote: >>> Stop in /usr/ports/x11/kdelibs3. > >> removed manually, if portmaster hasn't already done so. Here it looks >> like your new build of kde3libs is sloppily linking against the old >> version of kde3libs that you still have installed, and which still > > Obviously I meant kdelibs3 in the above -- this is starting to make me > dizzy, too. At this point I have to think that it is not cairo that is the issue, but something cairo is depending on that is referencing libpng.so.6. What I normally would have suggested, but failed to do in this case because cairo seemed like the obvious culprit, was to install sysutils/bsdadminscripts and run 'pkg_libchk -o | grep png" to track down ports that still depend on the old libpng. It will take a few minutes to run. I suspect something cairo links to (but is not in the listed depends) is needs to be re-built. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
