Re: When was the last ports tree that worked with RELENG_6?

2013-02-18 Thread Darren Pilgrim

On 2013-02-18 16:22, Darren Pilgrim wrote:

On 2013-02-16 08:06, Chris Rees wrote:

I think you may have some luck installing an up to date make(1) and
dialog(1) (or set NO_DIALOG=yes in make.conf) from stable/9 or
similar; many of the problems on 6 are caused by missing variable
modifiers.


I built and installed make from a RELENG_8_3 src tree.
Getting dialog was a bit harder because it requires libdialog and
libncurses.  I built a static-linked dialog on an RELENG_8_3 box and
dropped that in place.


Actually it appears the dialog binary doesn't work at all because I 
forgot the 6.x can't run an 8.x binary.  Without a working dialog 
binary, the ports system silently fails.  I did a make config on a port 
and it just gave me "options unchanged" and completed the config target 
without giving an error.


Make (even with an 8.3 make) complains of malformed conditionals in the 
src/gnu subtree, so I'm stuck on that one until I have time to dig. 
Reverting /usr/bin/dialog to the RELENG_6 binary makes config dialogs in 
ports work just fine.


___
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: When was the last ports tree that worked with RELENG_6?

2013-02-18 Thread Darren Pilgrim

On 2013-02-16 08:06, Chris Rees wrote:

I think you may have some luck installing an up to date make(1) and
dialog(1) (or set NO_DIALOG=yes in make.conf) from stable/9 or
similar; many of the problems on 6 are caused by missing variable
modifiers.


I built and installed make from a RELENG_8_3 src tree.
Getting dialog was a bit harder because it requires libdialog and 
libncurses.  I built a static-linked dialog on an RELENG_8_3 box and 
dropped that in place.  Seems to all be working fine now (updating ports 
to . as we speak).


Thanks!
___
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: PDF viewer that can rotate pages

2013-02-18 Thread Chad Perrin
On Mon, Feb 18, 2013 at 10:22:48AM -0800, Chip Camden wrote:
> Quoth Andrea Venturoli on Monday, 18 February 2013:
> > On 02/18/13 12:29, Anton Shterenlikht wrote:
> > >
> > > I never had problems rotating files with xpdf.
> > > Are you saying there are some PDF files that
> > > xpdf fails to rotate? Or are you saying your
> > > xpdf can never rotate pages?
> > 
> > Hmmm... my fault, sorry.
> > Now that I tried again xpdf can rotate my files... don't remember why I 
> > wasn't able the last time I tried (it's been eons).
> > Sorry again for the noise.
> > 
> > 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.

(Sorry about the double-send.  I think I accidentally replied directly
first.)

-- 
Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ]
___
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: Using just db44 for all instead of mixed usage of db41/db42/db44 (was: Re: mutt vs db44 // Bug in /usr/ports/Mk/bsd.database.mk ?)

2013-02-18 Thread Raphael Eiselstein
On Sun, Feb 17, 2013 at 06:14:28PM -0600, Scot Hetzel wrote:
> The reason that there are so many BDB versions in ports is that
> several of the functions had additional arguments added or swapped
> between versions.

What will happen if one binary is linked against db41 *and* db44 through
other libraries? ldd showed db41 and db44 for the mutt binary, what will
happen when calling one of these "unstable" functions? 

What is the difference between linking against db41 *plus* db44 or
linking just to db44 for all binaries? Conflicts? Overloading?
Segfaults?

How may I (automatically) check for incompatible db4x-Version?
compiler/linker errors? Runtime errors? Data structure errors in data
files? Data loss or corrupted db files?

Regards
Raphael

-- 
Raphael Eiselsteinhttp://rabe.uugrn.org/
xmpp:freiby...@gmx.de  | https://www.xing.com/profile/Raphael_Eiselstein   
GnuPG:E7B2 1D66 3AF2 EDC7 9828  6D7A 9CDA 3E7B 10CA 9F2D
.|.|.|.|.|.|.|..


signature.asc
Description: Digital signature


Re: graphics/gegl fails to update with portupgrade, works with make x 2

2013-02-18 Thread Koop Mast

On 18-2-2013 22:18, Torfinn Ingolfsen wrote:

The port graphics/gegl fail to upgrade with portupgrade (doing
'portupgrade -R gegl') but works if I cd to the port directory and run
make twice.
(I got the idea from another thread on the ports mailinglist)
Details:
tingo@kg-v2$ uname -a
FreeBSD kg-v2.kg4.no 8.3-STABLE FreeBSD 8.3-STABLE #6: Fri Apr 27
23:50:55 CEST 2012 r...@kg-v2.kg4.no:/usr/obj/usr/src/sys/GENERIC
amd64

tingo@kg-v2$ portversion -v gegl
gegl-0.1.8_4<  needs updating (port has 0.1.8_6)

HTH


Without the actually failure message we can't really do anything.

-Koop
___
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"


graphics/gegl fails to update with portupgrade, works with make x 2

2013-02-18 Thread Torfinn Ingolfsen
The port graphics/gegl fail to upgrade with portupgrade (doing
'portupgrade -R gegl') but works if I cd to the port directory and run
make twice.
(I got the idea from another thread on the ports mailinglist)
Details:
tingo@kg-v2$ uname -a
FreeBSD kg-v2.kg4.no 8.3-STABLE FreeBSD 8.3-STABLE #6: Fri Apr 27
23:50:55 CEST 2012 r...@kg-v2.kg4.no:/usr/obj/usr/src/sys/GENERIC
amd64

tingo@kg-v2$ portversion -v gegl
gegl-0.1.8_4<  needs updating (port has 0.1.8_6)

HTH
-- 
Regards,
Torfinn Ingolfsen
___
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: Is there an easy way to find out which port loads which library?

2013-02-18 Thread Chris Rees
On 18 Feb 2013 18:42, "Jeffrey Bouquet"  wrote:
>
>
>
> --- On Mon, 2/18/13, Chris Rees  wrote:
>>
>>
>> From: Chris Rees 
>>
>> Subject: Re: Is there an easy way to find out which port loads which library?
>> To: "Jeffrey Bouquet" 
>> Cc: "FreeBSD Mailing List" 
>> Date: Monday, February 18, 2013, 1:01 AM
>>
>> On 18 Feb 2013 05:35, "Jeffrey Bouquet"  wrote:
>> >
>> >
>> >
>> >
>> > >Subject: Re: Is there an easy way to find out which port loads which
>> library?
>> >
>> > >Bernard Higonnet wrote:
>> >
>> > > Is there a simple, direct, complete, and unequivocal way to find out
>> > > which port(s) install which libraries?
>> >
>> > >Something like this perhaps?
>> > ># grep libfoobar.so /usr/ports/*/*/pkg-plist
>> >
>> > >AvW
>> >
>> > None of these replies mention
>> > pkg which /usr/local/lib/libfoobar.so
>> > pkg_which /usr/local/lib/libfoobar.so
>> > ...
>> > I typically use one or both (still using /var/db/pkg after running pkg2ng
>> once a
>> > long time ago...)
>>
>> >Why???
>>
>> >Chris
>>
>> Unsure of the question.
>>
>> Why did I run pkg2ng?  I was uncognizant of all the immediate consequences.
>> Why did I revert?  Not ready to make /var/db/pkg disappear until I've seen
>> guides explaining the new usages which fit the present workflow here...
>>
>> Why do not I implement it at this time?  I've still too much to do in the 
>> short term
>> on a daily basis vs. implement anything new until I am one of the *last* to 
>> do so, so I would do it in the quickest and most expedient manner.
>>
>>
>> pkg_delete -f /var/db/pkg/rubygem-mime-types-1.19 && pkg_add 
>> rubygem-mime-types-1.21.tbz.
>> I don't have to know the 1.19 (the shell does).  I do not recall anyone 
>> mentioning how the
>> equivalent would work in a pkg system.  They may have, but if it was a 
>> reply, I
>> archived it somewhere, as I would prefer to switch all the machines I use 
>> weekly
>> all at once, and prefer to wait as long as expedient.

You can use pkg delete -x rubygem-mime-types, or pkg update && pkg
upgrade is really what you need there.

>> That works on legacy laptops as well as modern 4-core CPU, aided by the 
>> shell doing expansion, and I can type it without thinking, aided by the 
>> shell.
>> The subdirectory is directly available to grep, awk, less... without an .so.
>> I've not yet had time to implement a /var/db/pkg/ on  a machine running pkg
>> (by script maybe) so that it could continue.

Man pkg-query, but see below.

>> I've posted several times why the progress of /pkg/ has not been shown to 
>> [1] not slow down the workflow to which I am accustomed to upgrade multiple 
>> machines has not been reliably demonstrated... and edge cases in which the 
>> legacy method is
>> preferable.  Unfortunately, I ran out of time a long time ago to respond 
>> more in
>> depth; my views on the matter are scattered in the lists archives and forum 
>> archives
>> [further content redacted so as to not waste anyone's time.]

Shell autocomplete should be pretty easy to implement should you
choose, but given that many of the steps you describe are automated
anyway, it's hard to see any real advantage to manually manipulating
the data!

Rather than describing your current methods, you may be better off (in
a new thread) describing the *outcomes* that you would like, and we
can help you achieve them.

Chris
___
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: Is there an easy way to find out which port loads which library?

2013-02-18 Thread A.J. 'Fonz' van Werven
Not answering anyone in particular, but I feel compelled to point out that
as far as I know pkg_info only works with packages/ports that are already
installed (or at least created/downloaded), whereas the grep/find method
also works for finding out which not-yet-installed package/port *will*
install a certain file.

But do of course correct me if I'm mistaken.

AvW

-- 
I'm not completely useless, I can be used as a bad example.


pgpZfKsjDH2ta.pgp
Description: PGP signature


Re: PDF viewer that can rotate pages

2013-02-18 Thread Wojciech Puchar

xpdf can rotate 90,180,270 degrees

works great
___
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: PDF viewer that can rotate pages

2013-02-18 Thread Chip Camden
Quoth Andrea Venturoli on Monday, 18 February 2013:
> On 02/18/13 12:29, Anton Shterenlikht wrote:
> 
> > I never had problems rotating files with xpdf.
> > Are you saying there are some PDF files that
> > xpdf fails to rotate? Or are you saying your
> > xpdf can never rotate pages?
> 
> Hmmm... my fault, sorry.
> Now that I tried again xpdf can rotate my files... don't remember why I 
> wasn't able the last time I tried (it's been eons).
> Sorry again for the noise.
> 
> Thanks to you and also to Ruslan for his suggestion.
> 
>   bye
>   av.
> 
> ___
> 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"

zathura is a nice pdf reader, and you use 'r' to rotate the page.

-- 
.O. | Sterling (Chip) Camden  | http://camdensoftware.com
..O | sterl...@camdensoftware.com | http://chipsquips.com
OOO | 2048R/D6DBAF91  | http://chipstips.com


pgpPuUGgGYtY7.pgp
Description: PGP signature


Re: Is there an easy way to find out which port loads which library?

2013-02-18 Thread Jeffrey Bouquet


--- On Mon, 2/18/13, Chris Rees  wrote:

From: Chris Rees 
Subject: Re: Is there an easy way to find out which port loads which library?
To: "Jeffrey Bouquet" 
Cc: "FreeBSD Mailing List" 
Date: Monday, February 18, 2013, 1:01 AM

On 18 Feb 2013 05:35, "Jeffrey Bouquet"  wrote:
>
>
>
> 
> >Subject: Re: Is there an easy way to find out which port loads which
library?
> 
> >Bernard Higonnet wrote:
>
> > Is there a simple, direct, complete, and unequivocal way to find out
> > which port(s) install which libraries?
>
> >Something like this perhaps?
> ># grep libfoobar.so /usr/ports/*/*/pkg-plist
>
> >AvW
>
> None of these replies mention
> pkg which /usr/local/lib/libfoobar.so
> pkg_which /usr/local/lib/libfoobar.so
> ...
> I typically use one or both (still using /var/db/pkg after running pkg2ng
once a
> long time ago...)

>Why???

>Chris

Unsure of the question.

Why did I run pkg2ng?  I was uncognizant of all the immediate consequences.
Why did I revert?  Not ready to make /var/db/pkg disappear until I've seen 
guides explaining the new usages which fit the present workflow here...

Why do not I implement it at this time?  I've still too much to do in the short 
term
on a daily basis vs. implement anything new until I am one of the *last* to do 
so, so I would do it in the quickest and most expedient manner. 


pkg_delete -f /var/db/pkg/rubygem-mime-types-1.19 && pkg_add 
rubygem-mime-types-1.21.tbz.
I don't have to know the 1.19 (the shell does).  I do not recall anyone 
mentioning how the
equivalent would work in a pkg system.  They may have, but if it was a reply, I
archived it somewhere, as I would prefer to switch all the machines I use weekly
all at once, and prefer to wait as long as expedient.

That works on legacy laptops as well as modern 4-core CPU, aided by the shell 
doing expansion, and I can type it without thinking, aided by the shell.
The subdirectory is directly available to grep, awk, less... without an .so.
I've not yet had time to implement a /var/db/pkg/ on  a machine running pkg
(by script maybe) so that it could continue.

I've posted several times why the progress of /pkg/ has not been shown to [1] 
not slow down the workflow to which I am accustomed to upgrade multiple 
machines has not been reliably demonstrated... and edge cases in which the 
legacy method is
preferable.  Unfortunately, I ran out of time a long time ago to respond more in
depth; my views on the matter are scattered in the lists archives and forum 
archives
[further content redacted so as to not waste anyone's time.]

J. Bouquet

[1] I am not asking for anyone's efforts, 
nor trying to sound negative;
just trying to respond to the question with a wait-and-see 
viewpoint...




___
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"


Please commit ports/176207

2013-02-18 Thread Stefan Bethke
Hi,

if any ports committer would be willing to commit the maintainer's patch in 
ports/176207, I'd appreciate it!


Thanks,
Stefan

-- 
Stefan BethkeFon +49 151 14070811



___
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"


Fw: zimbra

2013-02-18 Thread Paul Pathiakis



- Forwarded Message -
From: Martin Solčiansky 
To: pathia...@yahoo.com 
Sent: Friday, February 15, 2013 2:56 AM
Subject: zimbra
 

hey,
I am trying to get a complete port built.

I've seen the incredible effort that you put in and I believe it to be VERY 
CLOSE to a complete port build.

I have been in contact with the FreeBSD ports people and some have expressed an 
interest in getting this to be a complete and sanctioned port.

Please tell me that you're interested in finishing this to completion.
once again, zimbra forums notification confuse me. i got private message 
notification on feb 15th, 6 days later :(.
i can tell you that zimbra on freebsd is the same zimbra you can run on linux 
nowadays. university mailserver has been happy for some time now :). however, 
with a complete port build there are some major issues:
1) '/opt/zimbra' is hardcoded. seriously, hardcoded in lots and lots of parts 
of code. you can do a patch that will change this but it's very very bad idea 
in the long run. the maintenance would kill you. putting stuff outside /usr 
does not comply with freebsd standards. you can circumvent via mount_null but i 
doubt that freebsd people will approve it.
2) some libraries/versions, perl modules are simply NOT available in the ports 
collection and if they are there you just cannot reuse them inside the base 
system since zimbra hardcodes stuff into them. there is a reason why zimbra 
team uses specific versions of the third party software and i somehow learnt 
the hard way :-). not to mention linking.
3) port upgrade would be a simple nightmare. you have to use the provided 
zimbra-upgrade script (or spent ages to do it your own way) and upgrade simply 
deletes all the binaries.. and replace them.

that being said, i am well capable of creating an initial port (hell, i started 
that long time ago and then just gave up) but i would need constant help. i 
don't have time to maintain it. and maybe i even lack some skill to do that. 
and i don't think that it can be done "properly".
some time ago i offered zimbra team i would rework their build process so that 
it becomes more.. transparent. well, i don't have the time now but prior to 
creating the port it would help a great deal if the zimbra team could just 
incorporate slight changes (include placeholders for the patch in the code, 
create ONE CONFIGURATION FILE FOR EVERYTHING (yes, caps)). that way you could 
do only slight alterations. simply change "master dir" and you are done (tbh, 
they use $ZIMBRA_HOME variable most of time.. and then.. they just switch to 
/opt/zimbra :))

so there you got your very first step. for several years the patch just "added" 
support for freebsd compilation while changing nothing for other platforms. i 
gave up in the last release and just hardcoded it 'cos once again i lack time. 
contact freebsd ports people, tell them to ask zimbra people to offer some help 
(they very friendly pre-vmware - dont know now).
the second step is finding someone who is interested in maintaining the port. i 
can do the patching for new versions but i simply won't handle the agenda 
(compatibility with other freebsd versions, compilation, alteration bla bla 
otherworsending in -ion).

i will try to prepare the newest zimbra version (8.0.2) patch and we can try 
the to make it happen :-). thing is.. i have no fucking idea why zimbra can't 
just do a proper supported commercial edition. it was proven that it runs on 
freebsd and it's somehow a very silly commercial model to exclude shitload of 
freebsd servers from their portfolio.

let's cure the disease, not the symptoms.

you can reach me on skype via solko_the_demigod handle. best of luck to you,

s.

PS (sorry about the html email but i just don't think that in these days anyone 
uses device without html support - and that comes from someone using fbsd for 
past 13 years)
___
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"

audio/audacity and audio/gstreamer-plugins-soundtouch fails due to SoundTouch

2013-02-18 Thread Joseph A. Nagy, Jr
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);
  ^~
/usr/local/include/soundtouch/SoundTouch.h:237:31: note: passing 
argument to parameter 'samples' here

const SAMPLETYPE *samples,  ///< Pointer to sample buffer.
  ^
effects/SoundTouchEffect.cpp:215:23: error: no matching member function 
for call to 'receiveSamples'

 mSoundTouch->receiveSamples(buffer2, outputCount);
 ~^~
/usr/local/include/soundtouch/FIFOSamplePipe.h:190:18: note: candidate 
function not viable: no known conversion from

  'float *' to 'SAMPLETYPE *' (aka 'short *') for 1st argument;
virtual uint receiveSamples(SAMPLETYPE *outBuffer, ///< Buffer 
where to copy output samples.

 ^
/usr/local/include/soundtouch/FIFOSamplePipe.h:203:18: note: candidate 
function not viable: requires 1 argument, but 2

  were provided
virtual uint receiveSamples(uint maxSamples   ///< Remove this many 
samples from the beginning of pipe.

 ^
effects/SoundTouchEffect.cpp:234:20: error: no matching member function 
for call to 'receiveSamples'

  mSoundTouch->receiveSamples(buffer2, outputCount);
  ~^~
/usr/local/include/soundtouch/FIFOSamplePipe.h:190:18: note: candidate 
function not viable: no known conversion from

  'float *' to 'SAMPLETYPE *' (aka 'short *') for 1st argument;
virtual uint receiveSamples(SAMPLETYPE *outBuffer, ///< Buffer 
where to copy output samples.

 ^
/usr/local/include/soundtouch/FIFOSamplePipe.h:203:18: note: candidate 
function not viable: requires 1 argument, but 2

  were provided
virtual uint receiveSamples(uint maxSamples   ///< Remove this many 
samples from the beginning of pipe.

 ^
effects/SoundTouchEffect.cpp:307:31: error: cannot initialize a 
parameter of type 'const SAMPLETYPE *'

  (aka 'const short *') with an lvalue of type 'float *'
  mSoundTouch->putSamples(soundTouchBuffer, blockSize);
  ^~~~
/usr/local/include/soundtouch/SoundTouch.h:237:31: note: passing 
argument to parameter 'samples' here

const SAMPLETYPE *samples,  ///< Pointer to sample buffer.
  ^
effects/SoundTouchEffect.cpp:373:17: error: no matching member function 
for call to 'receiveSamples'

   mSoundTouch->receiveSamples(outputSoundTouchBuffer, outputCount);
   ~^~
/usr/local/include/soundtouch/FIFOSamplePipe.h:190:18: note: candidate 
function not viable: no known conversion from

  'float *' to 'SAMPLETYPE *' (aka 'short *') for 1st argument;
virtual uint receiveSamples(SAMPLETYPE *outBuffer, ///< Buffer 
where to copy output samples.

 ^
/usr/local/include/soundtouch/FIFOSamplePipe.h:203:18: note: candidate 
function not viable: requires 1 argument, but 2

  were provided
virtual uint receiveSamples(uint maxSamples   ///< Remove this many 
samples from the beginning of pipe.

 ^
12 warnings and 5 errors generated.
gmake[1]: *** [effects/SoundTouchEffect.o] Error 1
gmake[1]: Leaving directory 
`/usr/ports/audio/audacity/work/audacity-src-2.0.3/src'

gmake: *** [audacity] Error 2
*** [do-build] Error code 1

Stop in /usr/ports/audio/audacity.
*** [build] Error code 1

Stop in /usr/ports/audio/audacity.

===>>> make failed for audio/audacity
===>>> Aborting update

===>>> Update for audio/audacity failed
===>>> Aborting update

Before I attempted this build, I did:
# cd /usr/ports/audio/audacity/
# make rmconfig

because previously I had gotten it to build with SoundTouch (which is 
installed). I cannot find any issues with either audacity or soundtouch 
in /usr/ports/UPDATING, either. Audacity isn't the only problem port I 
have because of SoundTouch. One of the gstreamer ports won't build 
because of it, either.


===>  Building for gstreamer-plugins-soundtouch-0.10.23,3
  CC libgstsoundtouch_la-plugin.lo
  CXXlibgstsoundtouch_la-gstpitch.lo
gstpitch.cc:384:17: error: no matching member function for call to 
'receiveSamples'
  priv->st->receiveSamples ((gfloat *) GST_BUFFER_DATA (buffer), 
samples);

  ~~^~
/usr/local/include/soundtouch/FIFOSamplePipe.h:190:18: note: candidate 
function not viable: no known conversion from
  'gfloat *' (aka 'float *') to 'SAMPLETYPE *' (aka 'short *') for 
1st argument;
virtual uint receiveSamples(SAMPLETYPE *outBuffer, ///< Buffer 
where to copy output samples.

 ^
/usr/local/include/soundtouch/FIFOSamplePipe.h:203:18: note: candidate 
function not viable: requires 1 argument, but 2

  were provided
virtual uint receiveSamples(uint maxSamples   ///< Remove this many 
samples from the be

FreeBSD ports you maintain which are out of date

2013-02-18 Thread portscout
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, you can
safely ignore the entry.

You will not be e-mailed again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
japanese/texinfo| 4.7 | 5.0
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

If wish to stop receiving portscout reminders, please contact
portsc...@portscout.freebsd.org

Thanks.
___
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: Fwd: Re: openfire start up problem

2013-02-18 Thread Pietro Cerutti
On 2013-Feb-17, 07:52, David Southwell wrote:
> Hi
Hi David,

> I am having trouble with openfire
> Getting error
> WARNING: no shebang line in COPYRIGHT
> 
> Here is the sequence:
> # service openfire start
> Starting openfire
> #service openfire status
> openfire is running as pid 9205
> #service openfire status
> /usr/local/etc/rc.d/openfire: WARNING no shebang line in COPYRIGHT
> openfire not running? (check /var/run/openfire.pid

I'm waiting for 3.8.1 to be released to update the port. In the
meanwhile, would you mind trying with 3.8.0?

http://people.freebsd.org/~gahr/openfire-3.8.0.diff

>  Original Message 
> From: - Sat Feb 16 12:01:41 2013
> X-Account-Key:account3
> X-UIDL:   4fe3828900015ada
> X-Mozilla-Status: 0011
> X-Mozilla-Status2:
> X-Mozilla-Keys:   
> Return-Path:  
> X-Original-To:da...@vizion2000.net
> Delivered-To: da...@vizion2000.net
> Received: from mail-vc0-f178.google.com (mail-vc0-f178.google.com 
> [209.85.220.178]) by dns1.vizion2000.net (Postfix) with ESMTP id 
> 09927119C52 for ; Sat, 16 Feb 2013 10:36:26 -0800 
> (PST)
> Received: by mail-vc0-f178.google.com with SMTP id m8so2820339vcd.37 
> for ; Sat, 16 Feb 2013 11:52:52 -0800 (PST)
> DKIM-Signature:   v=1; a=rsa-sha256; c=relaxed/relaxed; 
> d=nikolaypavlov.com; s=google; 
> h=x-received:mime-version:sender:in-reply-to:references:from:date 
> :x-google-sender-auth:message-id:subject:to:content-type; 
> bh=dlt1YmSqCBgeu9sMNMFDJiAAIW3Q4KFYQNHTaQOWLa4=; 
> b=V2Zl/fARLiPVJMfJ5NrT8HhgM1e4usPGBW+ChxEh933M6FOFQLsnKalcytt0kEyG44 
> BrJm58/eXsmnpLW+xgZuFPuIi0nGQs9B74P+aOtP8RJE/rEIqmxC7KDFUh8w1xztVzF8 
> DT0lYFNmo6Hbaz0ed5fGYj2JWqPsQtEY3tyy4=
> DKIM-Signature:   v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; 
> s=20120113; 
> h=x-received:mime-version:sender:in-reply-to:references:from:date 
> :x-google-sender-auth:message-id:subject:to:content-type; 
> bh=dlt1YmSqCBgeu9sMNMFDJiAAIW3Q4KFYQNHTaQOWLa4=; 
> b=gjmPvJTq4ZtlBFu1iAwzEhSVRlcg2qUQbtwFZ0mG/CrNnC/yzaab3OD9vNNHbCEvIo 
> 4RocrkUIVscqjA0p0iz3dQKd/euh3pzH+92/ivza5Rn2bHdXiWuvxRRJcoNo2ix0a/Io 
> gDGts96BJeXnmXfwFDQuyeSf7cGuq6jRB79HTUMkBtohsV6ChGYbI6RzQNyYQfscW8q2 
> XlQn40Slb+MugxQLiy+TGyp3p9UhZNc47P7RtzYejpIbRmP+o/z9igig3GMy68mn2ySB 
> 45lE6xwuOah+B7Cd6TgNzNtSnhN9/qrtTNUP+gArhRtzqcwpW0nqbaHRnHe031xk2BqC 6O8Q==
> X-Google-DKIM-Signature:  v=1; a=rsa-sha256; c=relaxed/relaxed; 
> d=google.com; s=20120113; 
> h=x-received:mime-version:sender:in-reply-to:references:from:date 
> :x-google-sender-auth:message-id:subject:to:content-type 
> :x-gm-message-state; bh=dlt1YmSqCBgeu9sMNMFDJiAAIW3Q4KFYQNHTaQOWLa4=; 
> b=Tgvb4PfsN461wXaizNI7fgmF+RfV2ZGDpyToZ2fVK2MvXKwR2QdwL2C5cGfDK629ws 
> 7l5ywHfydkuBL34q2cP8qSAEH1Rybebbc7fI+Z9cDF9+hsQMszdcGg5pJwA66jNmYf28 
> be/xiJ55gLa7EytmaNQ98I7qNvie4AtVi2BaT+9/hfikWT1G3kRRe+8QYJgbhWLX5JFA 
> E4OsDnEQPWMfqUwOSrlzaFaJT2vzV/8jzS0QuyhxQ0XiVEOB/IhbF6tJJuHUZmGIDn5i 
> Ld57HQnVSbTBS4Sh+pD/caa2F7yYeB9NpupUufpMawpaPGjC0mnTP1WwxOeys0caRSrc 9Z0Q==
> X-Received:   by 10.52.74.34 with SMTP id 
> q2mr7768464vdv.76.1361044372102; Sat, 16 Feb 2013 11:52:52 -0800 (PST)
> MIME-Version: 1.0
> Sender:   m...@nikolaypavlov.com
> Received: by 10.58.145.69 with HTTP; Sat, 16 Feb 2013 11:52:32 -0800 (PST)
> In-Reply-To:  <511fa30e.60...@vizion2000.net>
> References:   <511fa2a4.8040...@vizion2000.net> 
> <511fa30e.60...@vizion2000.net>
> From: Nikolay Pavlov 
> Date: Sat, 16 Feb 2013 21:52:32 +0200
> X-Google-Sender-Auth: uH_P5vJWyJ_jCe9M5F02qq1rNBM
> Message-ID: 
> 
> Subject:  Re: openfire start up problem
> To:   David Southwell 
> Content-Type: multipart/alternative; 
> boundary=20cf3071c7fc529f4a04d5dcd6c9
> X-Gm-Message-State: 
> ALoCoQl2SlWEPu/JYr8KnVAQO6ZhgF22wV+PprzpbnFSbD7P0nisMBgYZ4eY8bcrUKLOQbuTUsfV 
> 
> Status:   
> 
> 
> 
> Hi David,
> Actually I'm not maintainer of this port for a long time. You might want 
> to forward this to g...@freebsd.org.
> 
> Good luck.
> 
> Best regards, Nikolay Pavlov.
> 
> 
> On 16 February 2013 17:17, David Southwell  > wrote:
> 
> 
> Thought you might like a copy
> David
> 
>  Original Message 
> From: - Sat Feb 16 07:15:48 2013
> X-Mozilla-Status: 0001
> X-Mozilla-Status2:0080
> X-Mozilla-Keys:   
> Message-ID:   <511fa2a4.8040...@vizion2000.net>
> 
> Date: Sat, 16 Feb 2013 07:15:48 -0800
> From: David Southwell 
> 
> Organization: Vision Communications
> User-Agent:   Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0)
> Gecko/20130107 Thunderbird/17.0.2
> MIME-Version: 1.0
> To:   freebsd-ports@freebsd.org 
> Subject:  openfire start up problem
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> Co

Re: PDF viewer that can rotate pages

2013-02-18 Thread Andrea Venturoli

On 02/18/13 12:29, Anton Shterenlikht wrote:


I never had problems rotating files with xpdf.
Are you saying there are some PDF files that
xpdf fails to rotate? Or are you saying your
xpdf can never rotate pages?


Hmmm... my fault, sorry.
Now that I tried again xpdf can rotate my files... don't remember why I 
wasn't able the last time I tried (it's been eons).

Sorry again for the noise.

Thanks to you and also to Ruslan for his suggestion.

 bye
av.

___
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: PDF viewer that can rotate pages

2013-02-18 Thread Daniel Nebdal
Okular (from KDE4) can also do it ( View:Orientation:Rotate
(left|right) ), though that only qualifies as "small" if you've
already got KDE 4.

--
Daniel Nebdal

On Mon, Feb 18, 2013 at 12:16 PM, Andrea Venturoli  wrote:
> Hello.
>
> As per subject, I often get rotated PDFs, which are a pain to read.
> Neither xpdf, nor kpdf allow me to rotate the page again.
> Any suggestion for a reader that can?
> Ideally small with few requirements, but, failing that, I'll accept
> something big and fat, provided it's not Adobe Reader.
>
>  bye & Thanks
> av.
> ___
> 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"
___
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"


libreoffice

2013-02-18 Thread Wojciech Puchar
package works great (and far faster than openoffice) but still i would 
find quickstarter functionality that is available in windows openoffice 
useful.


I found loading a document taking milliseconds only when other document is 
already loaded, while otherwise it is few seconds.


any way to turn it on. Would be great to do this in gnome2 environment

my options

_OPTIONS_READ=libreoffice-3.6.5_2
_FILE_COMPLETE_OPTIONS_LIST=CPPUNIT CUPS DEBUG GNOME GTK2 GTK3 JAVA KDE4 
MERGELIBS MMEDIA PGSQL SDK SVG SYSTRAY WEBDAV

OPTIONS_FILE_UNSET+=CPPUNIT
OPTIONS_FILE_UNSET+=CUPS
OPTIONS_FILE_UNSET+=DEBUG
OPTIONS_FILE_SET+=GNOME
OPTIONS_FILE_SET+=GTK2
OPTIONS_FILE_UNSET+=GTK3
OPTIONS_FILE_UNSET+=JAVA
OPTIONS_FILE_UNSET+=KDE4
OPTIONS_FILE_SET+=MERGELIBS
OPTIONS_FILE_UNSET+=MMEDIA
OPTIONS_FILE_SET+=PGSQL
OPTIONS_FILE_UNSET+=SDK
OPTIONS_FILE_SET+=SVG
OPTIONS_FILE_SET+=SYSTRAY
OPTIONS_FILE_UNSET+=WEBDAV



other question - where are printers defined in libreoffice?

for me it would be enough to just pipe postscript output through given 
script.

___
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: PDF viewer that can rotate pages

2013-02-18 Thread Anton Shterenlikht
Date: Mon, 18 Feb 2013 12:16:36 +0100
From: Andrea Venturoli 
To: freebsd-ports@freebsd.org
Subject: PDF viewer that can rotate pages

Hello.

As per subject, I often get rotated PDFs, which are a pain to read.
Neither xpdf, nor kpdf allow me to rotate the page again.
Any suggestion for a reader that can?
Ideally small with few requirements, but, failing that, I'll accept 
something big and fat, provided it's not Adobe Reader.

  bye & Thanks
av.

I never had problems rotating files with xpdf.
Are you saying there are some PDF files that
xpdf fails to rotate? Or are you saying your
xpdf can never rotate pages?

Anton
___
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: PDF viewer that can rotate pages

2013-02-18 Thread Ruslan Makhmatkhanov

Andrea Venturoli wrote on 18.02.2013 15:16:

Hello.

As per subject, I often get rotated PDFs, which are a pain to read.
Neither xpdf, nor kpdf allow me to rotate the page again.
Any suggestion for a reader that can?
Ideally small with few requirements, but, failing that, I'll accept
something big and fat, provided it's not Adobe Reader.

  bye & Thanks
 av.


graphics/evince

--
Regards,
Ruslan

Tinderboxing kills... the drives.
___
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"


PDF viewer that can rotate pages

2013-02-18 Thread Andrea Venturoli

Hello.

As per subject, I often get rotated PDFs, which are a pain to read.
Neither xpdf, nor kpdf allow me to rotate the page again.
Any suggestion for a reader that can?
Ideally small with few requirements, but, failing that, I'll accept 
something big and fat, provided it's not Adobe Reader.


 bye & Thanks
av.
___
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"


Current unassigned ports problem reports

2013-02-18 Thread FreeBSD bugmaster
(Note: an HTML version of this report is available at
http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports .)

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.


S Tracker  Resp.  Description

o ports/176234[MAINTAINER] math/clipper: update to 5.1.0
f ports/176223feature request - ports/net/quagga
o ports/176209[new port]: misc/saaghar persian poetry software
f ports/176206update port: lang/urweb
o ports/176195[PATCH] games/cre: Set NO_WRKSUBDIR and BUILD_WRKSRC i
o ports/176194[PATCH] graphics/tifmerge: Simplify Makefile, remove d
o ports/176180mail/mailman broken without NLS
f ports/176178Implement upstream fix where multiple net/iaxmodem ins
f ports/176172graphics/povray37: /usr/local/bin/ld: disp_sdl.o: unde
o ports/176171[MAINTAINER] games/simsu: update to 1.2.3
f ports/176156Add multi-instance support to dns/nsd rc script
o ports/176130New port: www/cakephp23
f ports/176121[patch] sysutils/backuppc: add rrdtool pool statistic 
o ports/176107net-mgmt/collectd port update: adding zfs support
f ports/176106net-mgmt/collectd5 port update
o ports/176103[MAINTAINER] devel/gdb: Adding an option to disable TU
o ports/176096[NEW PORT] www/xibo-server: Xibo - Digital Signage (se
o ports/176095[NEW PORT] www/zikula: MVC web application framework (
f ports/176080multimedia/xbmc uses external ffmpeg for part of build
f ports/176075net/radsecproxy does not use openssl port
o ports/176044ports: print/ghostview (1.5_3) segfault/coredump
f ports/176016devel/libftdi LIB_DEPENDS for boost_system.4, current 
f ports/176012irc/inspircd fails to detect OpenSSL in base running r
o ports/176011[patch] update devel/boehm-gc from 7.1 to 7.2d
o ports/175998PERL_ARCHNAME != perl -V:archname in port Makefiles
o ports/175993new port net-mgmt/ostinato
f ports/175987audio/clementine-player 1.1.0_1  - album art not displ
f ports/175977[PATCH] mail/libpst: update to 0.6.58
f ports/175976[patch] Install desktop icon for games/boswars
o ports/175947[NEW PORT] www/sogo: Groupware server with a focus on 
o ports/175946[NEW PORT] devel/sope: An extensive set of GNUstep web
f ports/175944[PATCH] x11-wm/obmenu: OptionsNG, changed Makefile, De
f ports/175936[NEW PORT] x11-wm/lxmed: LXDE Main Menu Editor
f ports/175905[patch] games/rocksndiamonds: drop explicit smpeg depe
f ports/175884deskutils/cairo-dock deskutils/cairo-dock-plugins Plea
f ports/175879fail non-interactive installation sysutils/bsdstats
f ports/175875[MAINTAINER] www,russian/MT: update to 5.2.3,1
f ports/175868security/nessus-libnasl: nasl_crypto.c:25:10: fatal er
o ports/175863[NEW PORT] games/qtads: A cross-platform multimedia in
o ports/175853[NEW PORT] games/frobtads: TADS interpreter and the co
f ports/175848lang/rexx-regina: Update to 3.7 and Fix Build
f ports/175813[patch] mail/dovecot2 doesn't detect libstemmer or ext
f ports/175798FreeBSD 10 unable to build sysutils/fusefs-kmod
f ports/175772Update to finance/php-tclink
f ports/175765net-im/imspector ipfw support
o ports/175748New port: www/your-freedom A SOCKS proxy application
o ports/175744[MAINTAINER] sysutils/gigolo: [SUMMARIZE CHANGES]
f ports/175733devel/libatomic_ops:  Segmentation fault :  install  -
o ports/175723postfix+dovecot+ldap_sasl marked BROKEN
f ports/175677[update]: devel/eblob fix distinfo of github files
f ports/175656[patch] databases/sqlite3: update to 3.7.15.2
f ports/175621update net/dhcpcd
o ports/175620New port: devel/bashdb, Bash debugger
o ports/175612New port: devel/remake  version of GNU make utility th
f ports/175611sysutils/zfs-periodic package do not enable cron to ho
o ports/175552[NEW PORT] devel/chruby: Changes the current Ruby
f ports/175534[patch] net-mgmt/rackmonkey: Fix a redirect
o ports/175527security/expiretable doesn't work in FreeBSD 9.x
f ports/175523pkgng: mail/dovecot2-pigeonhole conflicts with mail/do
o ports/175451update port www/cas
f ports/175429audio/clementine-player: build error
o ports/175385dns/fastresolve does not compile
f ports/175373[patch] mail/getlive: need to update to late

devel/dconf failed to build with gcc 4.6.3

2013-02-18 Thread Quentin Schwerkolt

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

I've just try to build devel/dconf with gcc 4.6.3 FreeBSD 9.1-STABLE
amd64 r246821. The build faild with an unrecognized option '-avoid-version'.
So I had make a patch for allow build with gcc 4.6.3. It doesn't break
the port with clang and the base's gcc version.

Cordially.
Quentin Schwerkolt
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.19 (FreeBSD)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iQIcBAEBAgAGBQJRIfOyAAoJEMQ92ZzRWSo8iL0P/RnKxzVL/8talIcGQDu0xCCJ
u60y5+w+n/p9XeQmGeKCO42qR6lojGal85VSt5/DXL8RK4wo023A2eJrCZhL80pH
+jUZ8bnyC5RKzbPgEk25DpPEJuapT8/7uNePFwaghPrc/DA24JZwKvzj423qy+0G
BQlVyMSF9a9sP8p68E/IimllimW+B0vHgovT8JM0FESfwvK4u0N1uCu7EhoE9NHH
nsEbHf3o9AIAkZxbopt8CbR7XBI6JaTD90Km9X2u9sutKdIwJCqJLuyjIffwSE+L
+xvc6FImERFSmviF4mGnYBEvXYEC/GUW9gzQJVyKGcHprQEbiRyjtxRhAZgpcjGS
Md9LzaJ1Cmxe5iAOT5VziKrAPVfOMgKIkKgchou/4SJMTg2IN0VkDOCHrW3xpSSP
ExSrrd7iJEv/w0s1kDnk4DYckMZhOLLY/rA6dLBjAMg+2Ex+wHHjXDglkqnSAe8u
4tsB611qR3tgvA5XY7ComNk710W1PzXYBsArfgIfxFSt661oi6fZlnqNKOH30L+Z
G8GgURMJxn0I5NI/pe9yr2f/d182Z717ZVM6idLi9/HMxZSpW1NnRD6y0eYETvaa
D8v+ybxjgt0iuUsAA4wfzP64YIN5jhZzLkFf/yxdJhO/pRSZ+HHyWQFjPnBz66zx
YYrNUFG9uLOxI7JgDbgK
=Wh9y
-END PGP SIGNATURE-

--- gsettings/Makefile.in.orig  2013-02-18 10:04:22.579524810 +0100
+++ gsettings/Makefile.in   2013-02-18 10:04:52.377517488 +0100
@@ -194,7 +194,7 @@
 AM_CFLAGS = -std=c89 -Wall -Wmissing-prototypes -Wwrite-strings -fPIC -DPIC
 INCLUDES = -I$(top_srcdir)/common -I$(top_srcdir)/gvdb -I$(top_srcdir)/engine 
$(gio_CFLAGS)
 libdconfsettings_so_LDADD = $(gio_LIBS)
-libdconfsettings_so_LDFLAGS = -module -avoid-version -shared
+libdconfsettings_so_LDFLAGS = -module -shared
 libdconfsettings_so_SOURCES = \
../engine/dconf-engine.c\
../common/dconf-shmdir.c\
___
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: Is there an easy way to find out which port loads which library?

2013-02-18 Thread Chris Rees
On 18 Feb 2013 05:35, "Jeffrey Bouquet"  wrote:
>
>
>
> --- On Sun, 2/17/13, A.J. 'Fonz' van Werven  wrote:
>
> >From: A.J. 'Fonz' van Werven 
> >Subject: Re: Is there an easy way to find out which port loads which
library?
> >To: "Bernard Higonnet" 
> >Cc: freebsd-ports@freebsd.org
> >Date: Sunday, February 17, 2013, 9:21 AM
>
> >Bernard Higonnet wrote:
>
> > Is there a simple, direct, complete, and unequivocal way to find out
> > which port(s) install which libraries?
>
> >Something like this perhaps?
> ># grep libfoobar.so /usr/ports/*/*/pkg-plist
>
> >AvW
>
> None of these replies mention
> pkg which /usr/local/lib/libfoobar.so
> pkg_which /usr/local/lib/libfoobar.so
> ...
> I typically use one or both (still using /var/db/pkg after running pkg2ng
once a
> long time ago...)

Why???

Chris
___
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"