Hello.
For years I've been an happy user of FreeBSD + apcupsd + APC Smart-UPS 1500.
This has worked through various upgrades until a few days ago.
Right now my config is:
# uname -a
FreeBSD xx.x 9.0-RELEASE-p5 FreeBSD 9.0-RELEASE-p5 #2: Sat Dec 1
14:43:22 CET 2012
Hi,
I tried to build firefox on amd64 inside a 9-STABLE jail using
poudriere. I got the following build error:
The full build log is here:
http://people.freebsd.org/~rodrigc/ports/firefox-18.0.2%2c1.log.txt
The part that is causing the error is some C++ error related
to partial template
Hi!
I like to update opengtl on my system:
FreeBSD 9.1-RELEASE #0 r243826: Tue Dec 4 06:55:39 UTC 2012
r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386
FreeBSD clang version 3.1 (branches/release_31 156863) 20120523
Target: i386-unknown-freebsd9.0
Thread model: posix
Why it
Joseph A. Nagy, Jr wrote on 18.02.2013 18:52:
effects/SoundTouchEffect.cpp:209:31: error: cannot initialize a
parameter of type 'const SAMPLETYPE *'
(aka 'const short *') with an lvalue of type 'float *'
mSoundTouch-putSamples(buffer, block);
^~
Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated,
I have an issue with upgrading windowmaker in that it now pulls in
x11-wm/libwraster and they both want to install a man page in the same
place[0], unfortunately the proposed workaround[1] doesn't work. Anyone
have any other ideas? Again, I have done all the steps in the pr and
build fails as
On 11/02/2013 16:27, Burton, Steven wrote:
I have just installed netdot from the port on FreeBSD 9.1 REL and as
soon as I try to log into the web console, I get an error relating to
netdot.accessright not existing. Googling, it seems that this is fixed
in v 1.0.3. Is there any way of fixing an
2013/2/19 Joseph A. Nagy, Jr jnagyjr1...@gmail.com:
I have an issue with upgrading windowmaker in that it now pulls in
x11-wm/libwraster and they both want to install a man page in the same
place[0], unfortunately the proposed workaround[1] doesn't work. Anyone have
any other ideas? Again, I
Nick,
Thanks for that and for letting me know. Alas, the (new) PC I was
pretending was a test server has given up the ghost so it is perforce a
new install anyway.
Steve.
-Original Message-
From: Nick Hilliard [mailto:n...@foobar.org]
Sent: 19 February 2013 15:23
To: Burton, Steven
Cc:
On 02/19/13 09:45, Olivier Smedts wrote:
2013/2/19 Joseph A. Nagy, Jr jnagyjr1...@gmail.com:
I have an issue with upgrading windowmaker in that it now pulls in
x11-wm/libwraster and they both want to install a man page in the same
place[0], unfortunately the proposed workaround[1] doesn't work.
On 02/19/13 09:45, Olivier Smedts wrote:
2013/2/19 Joseph A. Nagy, Jr jnagyjr1...@gmail.com:
I have an issue with upgrading windowmaker in that it now pulls in
x11-wm/libwraster and they both want to install a man page in the same
place[0], unfortunately the proposed workaround[1] doesn't work.
# uname -a
FreeBSD alex-laptop 9.1-RELEASE FreeBSD 9.1-RELEASE #8: Tue Jan 22
14:00:27 CST 2013 root@alex-laptop:/usr/obj/usr/src/sys/ALEX-LAPTOP
amd64
/bin/sh /usr/local/bin/libtool --tag=CC--mode=link gcc -O2 -pipe
-fno-strict-aliasing -Wall -Wextra -Wno-sign-compare
The obvious issue is apparently that there's not an -linotify in
that argument list (or, alternatively, that is uses inotify functions
when it shouldn't) - though I'm far from sure why that would happen.
Do you have devel/libinotify installed? What does grep inotify
work/Window*/config.log say?
The games/xboing port builds fine, but when I try to run it I get the
following (and then it just exits):
(159)fonz@ace% xboing
XBoing - Please wait (insert gecos name), initialising xboing ...
XBoing - Error: Xlib Error: BadMatch (invalid parameter attributes)
Please read
On 02/19/13 10:39, Daniel Nebdal wrote:
The obvious issue is apparently that there's not an -linotify in
that argument list (or, alternatively, that is uses inotify functions
when it shouldn't) - though I'm far from sure why that would happen.
Do you have devel/libinotify installed? What does
Right, so it does find it - it just neglects to set the right flag
later. If I manage to both find the time and reproduce it, I can dig a
bit - though you're more likely to get a usful answer if someone that
actually knows about this chimes in in the meantime. :)
--
Daniel Nebdal
On Tue, Feb
On 02/19/13 11:38, Daniel Nebdal wrote:
Right, so it does find it - it just neglects to set the right flag
later. If I manage to both find the time and reproduce it, I can dig a
bit - though you're more likely to get a usful answer if someone that
actually knows about this chimes in in the
On 19.02.2013 18:44 (UTC+2), Joseph A. Nagy, Jr wrote:
On 02/19/13 11:38, Daniel Nebdal wrote:
Right, so it does find it - it just neglects to set the right flag
later. If I manage to both find the time and reproduce it, I can dig a
bit - though you're more likely to get a usful answer if
Hello again,
Just did an upgrade to FreeBSD 9.1 and I noticed that the apcupsd port
still has this crash and requires the patch. It would be fantastic if
the patch below could be integrated into the port for those of us who
are using 9606 SNMP cards.
Also adding a CC to po...@freebsd.org in
On 02/19/13 12:03, Rainer Hurling wrote:
On 19.02.2013 18:44 (UTC+2), Joseph A. Nagy, Jr wrote:
On 02/19/13 11:38, Daniel Nebdal wrote:
Right, so it does find it - it just neglects to set the right flag
later. If I manage to both find the time and reproduce it, I can dig a
bit - though you're
I have no problem integrating this patch, but it should be really
submitted upstream ...
On Tue, 19 Feb 2013 09:16:37 -0800
birch bi...@naturalpoint.com wrote:
Hello again,
Just did an upgrade to FreeBSD 9.1 and I noticed that the apcupsd
port still has this crash and requires the patch. It
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
On 02/19/13 12:52, er...@freebsd.org wrote:
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the
On Sun, 17 Feb 2013 15:56:26 -0600, Chris Rees utis...@gmail.com wrote:
Most shells won't allow an argument list that long.
% find /usr/ports -depth 3 -name pkg-plist -exec grep libfoobar.so \{} \;
has been shown to be faster than hacking around arg list limits with
echo |
xargs.
The
On 19 February 2013 19:00, Mark Felder f...@feld.me wrote:
On Sun, 17 Feb 2013 15:56:26 -0600, Chris Rees utis...@gmail.com wrote:
Most shells won't allow an argument list that long.
% find /usr/ports -depth 3 -name pkg-plist -exec grep libfoobar.so \{} \;
has been shown to be faster than
Sure, I will do that as well.
It looks like not much development has happened since late 2011, so who
knows when they will push out their next release.
Ion-Mihai Tetcu wrote on 2/19/2013 10:21 AM:
I have no problem integrating this patch, but it should be really
submitted upstream ...
On
On 19 February 2013 18:56, Joseph A. Nagy, Jr jnagyjr1...@gmail.com wrote:
On 02/19/13 12:52, er...@freebsd.org wrote:
** The following ports have a version number that sorts before a previous
one **
For many package tools to work correctly, it is of utmost importance
that
version
On 02/19/13 13:48, Chris Rees wrote:
On 19 February 2013 18:56, Joseph A. Nagy, Jr jnagyjr1...@gmail.com wrote:
On 02/19/13 12:52, er...@freebsd.org wrote:
** The following ports have a version number that sorts before a previous
one **
For many package tools to work correctly, it is of
A.J. 'Fonz' van Werven f...@skysmurf.nl writes:
The games/xboing port builds fine, but when I try to run it I get the
following (and then it just exits):
(159)fonz@ace% xboing
XBoing - Please wait (insert gecos name), initialising xboing ...
XBoing - Error: Xlib Error: BadMatch
On Mon, Feb 18, 2013 at 10:50 PM, Koop Mast k...@rainbow-runner.nl wrote:
Without the actually failure message we can't really do anything.
Hm, I forgot to include the error - sorry about that.
it is the exact same problem as the one in the earlier thread about gegl.
this:
Hallo Lowell Gilbert,
(159)fonz@ace% xboing
XBoing - Please wait (insert gecos name), initialising xboing ...
XBoing - Error: Xlib Error: BadMatch (invalid parameter attributes)
I'd say it's exactly the sort of thing to include the maintainer on,
even if you're trying to not
Dirk Meyer wrote:
Please try to start it with:
xboing -usedefcmap
That fixed it, thanks. Perhaps it ought to be added to the problems.doc
file?
AvW
--
I'm not completely useless, I can be used as a bad example.
pgpSis_K8SkBS.pgp
Description: PGP signature
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
Thanks to you and also to Ruslan for his suggestion.
zathura is a nice pdf reader, and you use 'r' to rotate the page.
High five. I came here to say this.
$zathura filename
error: could not open plugin directory: /usr/local/lib/zathura
error: unknown file type
just compiled from ports
Quoth Wojciech Puchar on Wednesday, 20 February 2013:
Thanks to you and also to Ruslan for his suggestion.
zathura is a nice pdf reader, and you use 'r' to rotate the page.
High five. I came here to say this.
$zathura filename
error: could not open plugin directory:
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
** The following ports have a version number that sorts before a previous one **
For many package tools to work correctly, it is of utmost importance that
version numbers of a port form a monotonic increasing sequence over time.
Refer to the FreeBSD Porter's Handbook, 'Package Naming
38 matches
Mail list logo
