Re: new port of bonfire

[Lars Engels]

On Thu, Jul 06, 2006 at 04:16:05PM -0300, Sergio Lenzi wrote:
> Hello all..
> 
> I have made a port of bonfire  http://perso.orange.fr/bonfire/
> and would like to publish it in the ports collection
> 
> After reading the ports documentation I 
> found nothing abou publishing it in the ports collection
> 
> Can someone, please,   give me a direction on
> how o publish the port?  or submit it to a commiter

Hi Sergio!

You have to send it with 'send-pr'. It's described here:
http://www.freebsd.org/doc/en/books/porters-handbook/porting-submitting.html


Lars


pgptPP0Hz4eH4.pgp
Description: PGP signature

Re: multimedia/pwcbsd fails on up to date current.

[Lars Engels]

On Thu, Jun 04, 2009 at 04:25:03PM +0200, Ganael LAPLANCHE wrote:
> On Thu, 04 Jun 2009 08:56:43 -0500, eculp wrote
> 
> Hello,
> 
> > I can't compile multimedia/pwcbsd on my laptop running current with  
> > ports, kernel, userland up to date.
> 
> See this mail :
> 
> http://lists.freebsd.org/pipermail/freebsd-usb/2009-May/006866.html
> 
> USB2 Symbols have been renamed. You'll have to fix the port's patch to make it
> build under recent -current.

Thanks for the error report. I'll take a look at this.


pgpZhazPgiTIn.pgp
Description: PGP signature

Re: multimedia/pwcbsd fails on up to date current.

[Lars Engels]

On Thu, Jun 04, 2009 at 08:56:43AM -0500, eculp wrote:
> I can't compile multimedia/pwcbsd on my laptop running current with  
> ports, kernel, userland up to date.
> 
> It finishes with:
> 
> pwc.c:155: warning: passing argument 3 of 'usb2_lookup_id_by_uaa' from  
> incompatible pointer type
> pwc.c: In function 'pwc_attach':
> pwc.c:173: error: dereferencing pointer to incomplete type
> pwc.c:174: error: dereferencing pointer to incomplete type
> pwc.c:175: error: dereferencing pointer to incomplete type
> pwc.c:180: error: dereferencing pointer to incomplete type
> pwc.c:181: error: dereferencing pointer to incomplete type
> pwc.c:184: error: dereferencing pointer to incomplete type
> pwc.c: In function 'pwc_detach':
> pwc.c:296: warning: passing argument 1 of 'usb2_transfer_unsetup' from  
> incompatible pointer type
> pwc.c: In function 'pwc_close':
> pwc.c:460: warning: passing argument 1 of  
> 'usb2_set_alt_interface_index' from incompatible pointer type
> pwc.c: In function 'pwc_try_video_mode':
> pwc.c:600: warning: passing argument 1 of 'usb2_transfer_unsetup' from  
> incompatible pointer type
> pwc.c:618: warning: passing argument 1 of  
> 'usb2_set_alt_interface_index' from incompatible pointer type
> pwc.c:626: warning: passing argument 1 of 'usb2_transfer_setup' from  
> incompatible pointer type
> pwc.c:626: warning: passing argument 3 of 'usb2_transfer_setup' from  
> incompatible pointer type
> pwc.c:632: warning: passing argument 1 of 'usb2_transfer_start' from  
> incompatible pointer type
> pwc.c: In function 'pwc_isoc_rx_callback':
> pwc.c:680: error: dereferencing pointer to incomplete type
> pwc.c:682: error: dereferencing pointer to incomplete type
> pwc.c:688: error: dereferencing pointer to incomplete type
> pwc.c:689: error: dereferencing pointer to incomplete type
> pwc.c:689: error: dereferencing pointer to incomplete type
> pwc.c:691: error: dereferencing pointer to incomplete type
> pwc.c:691: error: dereferencing pointer to incomplete type
> pwc.c:692: warning: passing argument 1 of 'usb2_start_hardware' from  
> incompatible pointer type
> pwc.c:695: error: dereferencing pointer to incomplete type
> pwc.c: In function 'pwc_isoc_handler':
> pwc.c:710: error: dereferencing pointer to incomplete type
> pwc.c:729: error: dereferencing pointer to incomplete type
> pwc.c:730: error: dereferencing pointer to incomplete type
> pwc.c:743: error: dereferencing pointer to incomplete type
> pwc.c: In function 'pwc_free_buffers':
> pwc.c:953: warning: passing argument 1 of 'usb2_transfer_unsetup' from  
> incompatible pointer type
> *** Error code 1
> 
> Stop in /usr/ports/multimedia/pwcbsd/work/pwcbsd.
> *** Error code 1
> 
> This is probably related to the usb changes hopefully related to  
> getting my junky Crystal Eye Webcam working ;)
> 
> thanks,

Can you please test 
http://bsd-geek.de/FreeBSD/pwcbsd_usbfix.patch ?


Lars


pgpJZ7hIB03r7.pgp
Description: PGP signature

Re: Dropping maintainership for sysutils/zfs-snapshot-mgmt

[Lars Engels]

On Tue, Jul 28, 2009 at 11:36:45AM +0200, Marius Nünnerich wrote:
> 2009/7/28 Marcin Simonides :
> > Hello,
> >
> > I am the maintainer and author of zfs-snaphot-mgmt port - a crude (and a bit
> > buggy) script for automatic snapshot creation and removal on ZFS.
> > Since I am no longer using FreeBSD I cannot keep neither the port nor the
> > script itself up-to-date.
> >
> > If someone, preferably one of the users, would like to take over the script
> > and/or the port please contact me off the list.
> > --
> > Marcin Simonides
> 
> I'll take it. Thanks for your good work so far! I'm using it hourly ;)

Thanks for the work you put in the port, Marcin.

I just passed its maintainership to Marius.


Lars


pgpu5t0P2WFJU.pgp
Description: PGP signature

Re: SourceForge changing file distribution scheme!

[Lars Engels]

On Tue, Aug 11, 2009 at 07:55:00PM +0400, Dmitry Marakasov wrote:
> * Erwin Lansing (er...@freebsd.org) wrote:
> 
> > > I've noticed that SF is changing file distribution scheme significantly,
> > > and I guess that will affect many ports and maybe infrastructure.
> > 
> > I fear the same, unfortunately.  However, I haven't as yet been able to
> > identify a consistency in the new scheme.

There can also be very weird subdir names: :-(
http://downloads.sourceforge.net/project/tvbrowser/TV-Browser (Java 5 and 
higher)/2.7.4/tvbrowser-2.7.4.tar.gz



pgpqr87M1qoC7.pgp
Description: PGP signature

Re: acroread9 crashes after maybe 10 seconds of operation.

[Lars Engels]

On Thu, Jun 18, 2009 at 01:49:40AM +0900, Hiroki Sato wrote:
> Hiroki Sato  wrote
>   in <20090617.141203.07900852@allbsd.org>:
> 
> hr> Robert Huff  wrote
> hr>   in <18997.22089.242834.29...@jerusalem.litteratus.org>:
> hr> ro>   Um.
> hr> ro>   Are there plans to get it to work with something more recent?
> hr> ro> I was under the (uninformed) impression linux_base-fc-4 was, ah,
> hr> ro> workable but no longer favored.
> hr>
> hr>  The ports collection still assumes fc4 as the default, so I think it
> hr>  is the primary target.
> hr>
> hr>  Anyway, I will try other configurations including one in your report.
> hr>  I guess the issue is due to some incomplete (or not-fully-compatible)
> hr>  compat-layer implementations of features available in Linux 2.6.x.
> 
>  I could reproduce the symptom (RSException), but this has also been
>  reported on Linux: http://forums.adobe.com/message/1931692.  The
>  release note of 9.1.2 says it is solved but it remains as far as I
>  can check.
> 
>  BTW, could you give it a try to set sysctl
>  compat.linux.osrelease=2.4.2 and let me know if it works or not?

Any news on this?
I never got acroread9 to work. It always crashes for me.
I am using linux_base-f10 and HEAD.
Setting  compat.linux.osrelease=2.4.2 results in 
FATAL: kernel too old



pgpDpQsfDLLAt.pgp
Description: PGP signature

Re: OpenOffice.org packages

[Lars Engels]

Quoting Gary Kline :


On Thu, Nov 26, 2009 at 04:39:19AM -0600, Scot Hetzel wrote:

On 11/26/09, Gary Kline  wrote:
>  > Looks like all the OpenOffice ports have a line like this:
>  >   JAVA_VENDOR=freebsd bsdjava openjdk
>
>
>
> Okay, so what does this mean I'm going to have to find and
> build from java-land from Sun?  Anything??
>
>
It defines which java ports are allowed to satisfy the java build/run
dependancy.

According to /usr/ports/Mk/bsd.java.mk, any one of these ports will
satisfy the dependancy on java.

freebsd  java/diablo-jdk15, java/diablo-jdk16
bsdjava  java/jdk13 thru java/jdk16
openjdk6   java/openjdk6

If you install openjdk6 before building Open Office, it will use
openjdk6 and you won't need to download any files from Sun.


Arrgh, welli just mucked around for 90 mins d/loading
diablo16, plus the tzone-2009p.zip, but the build fumbles.

i'll build openjdk6 right now.

thanks.

gary

PS:  i may as well ask you if there are other things-java in
the open realm...  i',m thinking of the kaffee portsand so
forth.



The nice thing about openjdk6 is that you can use pkg_add -r ;-)


pgpNEiuoE2fOF.pgp
Description: PGP Digital Signature

Re: [Call For Testing] New version - aMSN-0.98.1

[Lars Engels]

On Tue, Dec 01, 2009 at 03:00:02AM +0100, Frank Steinborn wrote:
> Sylvio Cesar wrote:
> > Hi folks,
> > 
> > I would like to invite everyone to test the newest version of aMSN.
> > This version has support for video conferencing and audio conferencing, is
> > using tk and tcl 8.6 with support for threads.
> 
> Running fine here for the last 24 hours and I'm forced to be a heavy
> msn-user. Everything is functional, video-call is fine too (but only
> incoming, don't have a cam myself).
> 
> Thanks for it, I might even switch from emesene.

Works for me, also. I can setup my pwcbsd-based cam, but cannot connect
to the other client which can be because of my firewall settings.



pgpzHDdjxcHXK.pgp
Description: PGP signature

Re: New version of the fakeroot patch

[Lars Engels]

On Tue, Dec 15, 2009 at 09:09:22AM -0700, Warren Block wrote:
> A suggestion: USE_FAKE is not descriptive.  It doesn't tell what is fake 
> or what happens.  I'm not sure fake is the even the right word.
> 
> USE_FAKEROOT is better, but still ambiguous: it's not really fake, and 
> "root" can mean too many things.

Isn't this function also called fakeroot on OpenBSD?


pgpbvrbhlfgix.pgp
Description: PGP signature

Re: mplayer from SVN

[Lars Engels]

Quoting Frank Staals :


On 12/28/09 15:47, eculp wrote:

On Fri, 11 Dec 2009, Denis Shaposhnikov wrote:


Hello,

Does anybody have a port for building mplayer from SVN?

Thanks!

On a sidenote: I used to build mplayer from svn regularly on my
previous system. Updating mplayer usually was quite painless. Simply
'svn up && ./configure --prefix=/usr/local/mplayersvn && gmake && gmake
install'. In 99% of the cases rebuilding went perfectly; no patches
required or anything, and I rebuilded mplayer almost weekly. This was
on a i386 system by the way, on my current amd64 install I run into
problems trying to compile the current svn snapshots.

I know it is not as nice as simply having a port. But if you realy need
the svn-releases for some feature XYZ it may be a (temporary) solution.



Are there any killer features missing in our old version from ports?


pgpQZfC0V98HD.pgp
Description: PGP Digital Signature

Re: mplayer from SVN

[Lars Engels]

On Tue, Dec 29, 2009 at 08:03:21PM +0100, Michal Varga wrote:
> On Tue, Dec 29, 2009 at 7:05 PM, Frank Staals  wrote:
> > On 12/29/09 14:31, Lars Engels wrote:
> >>
> >> Quoting Frank Staals :
> >>
> >>> I know it is not as nice as simply having a port. But if you realy need
> >>> the svn-releases for some feature XYZ it may be a (temporary) solution.
> >>
> >>
> >> Are there any killer features missing in our old version from ports?
> >
> > I don't really know. The reason that I used svn snapshots in the past was
> > that my machine in combination with the mplayer port was unable to decode
> > relatively high res h264 video while with the svn version there were some
> > improvements which did make it possible. But that is a long time ago.
> >
> Related to that, VDPAU ( http://en.wikipedia.org/wiki/VDPAU ) is
> definitely "the killer feature", though I'm not sure how well (and if)
> it works on FreeBSD. For what I know, it works miracles on Linux
> (well, at least Linux people say that). Quick google turned out this,
> so I guess it's a start:
> http://forums.freebsd.org/showthread.php?t=4756
> 
> For anything else "killer-grade", I'm not really sure, but since the
> dawn of time, mplayer code base has always been a bit flaky (well, "a
> bit" itself is a bit too generous here). I guess all of us keep at
> least one other "backup" movie player (Gnome's Totem, XINE before
> that, etc.) for files that make mplayer die horribly in a ball of fire
> (recent youtube formats, I'm looking at you!) and vice versa - so one
> can reasonably assume that sticking to a 3-year old code base is not
> the very best we could do here and in the long term, unmanageable. It
> will only get worse.. 4 years? 5 years? Eventually other apps that use
> mplayer as their backend will start to fail, dtto various mencoder
> frontends (I'd say 'video editing software', if we only had any), and
> we will get stuck with gstreamer-powered crap (ok, not exactly bad,
> but even now in 2009, it's light years far from anything that 3-year
> old mplayer can do, and, you know, even a bad timed sneeze or an
> unfavorable lunar phase can make Totem crash).

Thanks a lot for the information on the new features.
I hope we can find a solution to use the svn version.


pgp69vrm7l2EG.pgp
Description: PGP signature

Re: Binary packages for releases and portupgrade

[Lars Engels]

On Wed, Jan 06, 2010 at 08:46:38PM +0100, Peter Ulrich Kruppa wrote:
> On Wed, 6 Jan 2010, Martin Cracauer wrote:
> >
> > So the verdict is to hunt down OpenOffice packages manually and
> > install them so that portupgrade ignores them, then go from there.
> >
> > ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/
> > seems to have what `portupgrade -P` should expect, right?
> >
> > So I wouldn't have to move from stable to release+sec.
> I wonder if people who succeed in building OOo (happens about 
> twice a year to me) could put their packages on some kind of ftp 
> server. From their mailing list I get the impression OOo-porting 
> team could need all kind of help.

There are already some builds (english and german) at
http://wiki.bsdforen.de/anwendungen/openoffice_aus_inoffiziellen_paketen

They're updated on a unregularly basis.

Cheers
Lars


pgp24RDPMrV4W.pgp
Description: PGP signature

Re: mplayer update

[Lars Engels]

On Thu, Jan 07, 2010 at 12:33:17PM +0200, Iasen Kostov wrote:
> Can You pleas update mplayer to something more recent, current version is
> last updated '12 Dec 2007' which is more than 2 years ago and the last
> update on their site is from '2009-11-01', There are a lot of new features
> and fixes like VDPAU, .mkv seek and many many many more. I hate to have them
> all on my windoze version and not on the FreeBSD one.

There have been several discussions on this topics during the last
weeks. The port should be updated, soon.


pgpA76PgOQU3k.pgp
Description: PGP signature

Re: Wanting to test video4bsd on todays cvsup and build but can't compile the pwcbsd port.

[Lars Engels]

On Tue, Jan 12, 2010 at 11:59:26AM -0600, eculp wrote:
> I am running todays current complete with cvsup, build and install  
> kernel and userland.
> 
> # uname -a
> FreeBSD ed.local.net.mx 9.0-CURRENT FreeBSD 9.0-CURRENT #420: Tue Jan  
> 12 07:13:52 CST 2010  
> r...@ed.local.net.mx:/usr/obj/usr/src/sys/ENCONTACTO  i386
> 
> When I try to build the pwcbsd port I get:
> 
> # make
> ===>  Building for pwcbsd-1.4.1_6
> make -f Makefile.kld all
> Warning: Object directory not changed from original  
> /usr/ports/multimedia/pwcbsd/work/pwcbsd
> cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE  
> -nostdinc   -I. -I@ -I@/contrib/altq -finline-limit=8000 --param  
> inline-unit-growth=100 --param large-function-growth=1000 -fno-common   
> -mno-align-long-strings -mpreferred-stack-boundary=2  -mno-mmx  
> -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding  
> -fstack-protector -std=iso9899:1999 -fstack-protector -Wall  
> -Wredundant-decls -Wnested-externs -Wstrict-prototypes   
> -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef  
> -Wno-pointer-sign -fformat-extensions -c pwc.c
> pwc.c:576: error: conflicting types for 'pwc_mmap'
> pwc.c:47: error: previous declaration of 'pwc_mmap' was here
> *** Error code 1
> 
> Stop in /usr/ports/multimedia/pwcbsd/work/pwcbsd.
> *** Error code 1
> 
> Stop in /usr/ports/multimedia/pwcbsd/work/pwcbsd.
> *** Error code 1
> 
> Stop in /usr/ports/multimedia/pwcbsd.
> 
> 
> Any help or suggestions appreciated.
> 
> ed

Did you enable this in OPTIONS?
Enable mmap support (MAY CRASH YOUR SYSTEM) 




pgpyAQrHQ8TvM.pgp
Description: PGP signature

Re: utmpx fallout - fix for mrxvt-devel

[Lars Engels]

On Fri, Jan 15, 2010 at 12:43:18PM +0100, Gary Jennejohn wrote:
> Here's an (inlined) patch to fix mrxvt-devel after the move to utmpx.
> 
> The maintainer (lme@) copied per Cc.
> 
> --- Makefile.orig 2010-01-15 12:23:35.0 +0100
> +++ Makefile  2010-01-15 12:27:54.0 +0100
> @@ -37,6 +37,10 @@
>  
>  .include 
>  
> +.if ${OSVERSION} >= 97
> +CONFIGURE_ARGS+= --disable-utmp --disable-wtmp
> +.endif
> +
>  .if defined(WITH_JAPANESE)
>  CONFIGURE_ARGS+= --enable-xim --enable-cjk --with-encoding=eucj
>  .endif

Hi Gary,

thanks for the patch. I'll take a look at it this evening.

Lars


pgpOmtyvoAgi3.pgp
Description: PGP signature

Re: Compile xmind for FreeBSD

[Lars Engels]

On Fri, Jan 22, 2010 at 01:39:32PM +0100, Guy Brand wrote:
> Hello,
> 
> 
> Has anyone here ever tried to build XMind (http://www.xmind.net) for
> FreeBSD? I tried several times, but I must confess I'm not comfortable
> with Eclipse, so I haven't succeeded yet. I've sent a request to the
> XMind feedback address asking for a FreeBSD version of their tool but
> not even their MAILER DAEMON answered. XMind has a better UI than the
> most common Freemind mind mapping tool, and it's also available (both
> in an Open Source and a commercial version) for several platforms.

If it's a Java app, you don't need to compile it. Just create a port for
their "portable zip file".



-- 
Lars


pgpNqMhlMpAxc.pgp
Description: PGP signature

Re: Flash and Firefox 3.6. Should flash work for sites like YouTube?

[Lars Engels]

On Wed, Feb 10, 2010 at 01:35:52PM -0600, eculp wrote:
> I have just installed Firefox3.6 and reinstalled nspluginwrapper-devel  
> a have run  nspluginwrapper -v -a -i but YouTube still gives me the:
> 
> Hello, you either have JavaScript turned off or an old version of  
> Adobe's Flash Player. Get the latest Flash player.
> 
> message.  Do I need to do something more than I did with 3.5?

For the records:
Yesterday I updated to FF 3.6 on Current and did not have to rebuild
the flash port or nspluginwrapper.


pgp4i5fuwPnDi.pgp
Description: PGP signature

Re: sysutils/syslog-ng3 processes

[Lars Engels]

On Sun, Feb 28, 2010 at 08:58:55AM -0800, Vince Valenti wrote:
> 
> 
> I'm actually no longer the maintainer of the port, but if you check
> sockstat, you will notice the second process is the one that is actually
> listening to the network, etc: 
> 
> # ps auxww|grep syslog
> root 29196 0.0 0.0
> 5320 2172 ?? I 8:40AM 0:00.00 /usr/local/sbin/syslog-ng -p
> /var/run/syslog.pid
> root 29197 0.0 0.0 5320 2432 ?? Ss 8:40AM 0:00.04
> /usr/local/sbin/syslog-ng -p /var/run/syslog.pid 
> 
> # sockstat|grep
> syslog
> root syslog-ng 29197 3 dgram /var/run/log
> root syslog-ng 29197 5
> stream /var/db/syslog-ng.ctl
> root syslog-ng 29197 6 dgram
> /var/run/logpriv
> root syslog-ng 29197 7 udp4 *:514 *:* 
> 
> My guess is that
> this is by design. In fact, I've checked syslog-ng on a Linux machine
> (gasp) and it also runs two processes: 
> 
> root 30648 0.0 0.0 29428 868 ? S
> 04:02 0:00 supervising syslog-ng 
> root 30649 0.0 0.0 35984 2404 ? Ss 04:02
> 0:06 /opt/syslog-ng/sbin/syslog-ng --no-caps 

IIRC I've also seen that on Solaris.


pgpPO07AYYARD.pgp
Description: PGP signature

Re: Dynamic plists

[Lars Engels]

On Thu, Apr 22, 2010 at 08:18:29AM +0200, Dominic Fandrey wrote:
> On 22/04/2010 01:45, Rob Farmer wrote:
> > I maintain math/scilab and am preparing to update it. This port has a
> > huge plist (slightly under 15000 lines), hundreds of which change
> > depending on what options are selected. It is a bit of a pain to
> > update. The porters handbook makes vague reference to dynamic plists -
> > so I was wondering, would this be a good idea? And if so, what is the
> > best way to make one?
> 
> You normally base it on the output of
> ${FIND} -s PATH -type f
> ${FIND} -d PATH -type d | ${SED} 's,^,@dirrm ,'
> 
> Of course there's normally more to it, but that's the basic principle.
> 

Or use auto-plist:
http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi/portstools/auto-plist/


pgpZtEHAqOxKr.pgp
Description: PGP signature

Re: Port request

[Lars Engels]

On Fri, May 28, 2010 at 12:11:10PM +0200, David DEMELIER wrote:
> 
> I agree, personally I would prefer a wpa_supplicant / dhclient
> graphical user interface instead of the sucky NetworkManager. For the
> moment there is sysutils/wifimgr iirc but it's a quite unstable.
> 
> wpa_supplicant does everything, scanning for access points
> automatically even you don't have X running, all WPA means of
> associations, it's just perfect.

Take a look at this:
> make -C /usr/ports quicksearch name=pcbsd-
Port:   pcbsd-netmanager-8.0_1
Path:   /usr/ports/net/pcbsd-netmanager
Info:   PC-BSD Networking Utilities for KDE4



pgptiwPkuNSNf.pgp
Description: PGP signature

Re: Solutions for the PR load problem

[Lars Engels]

On Fri, Jul 09, 2010 at 10:51:01PM +0200, Dominic Fandrey wrote:
> On 09/07/2010 22:00, Shaun Amott wrote:
> > 
> > I'm not sure how many non-committers were aware of / given access to tb3
> > and tb4 when they were around, but if tinderbox were used as a matter of
> > course, it would, I believe go some way to speeding things up.
> > 
> 
> So if I set up a private tinderbox and provide amd64 and i386
> 6-/7-/8-stable logs with every PR I submit it would hasten the
> processing of my PRs?

The more complex a port is and the more dependencies it has the more
work a committer has to check if the PR is error-free.
Having TB-Logs would prove that the port builds fine, and the PR is more
 likely to be taken.

It's also better for the submitter as he can see if he has made any
errors.


pgpbNcxPoIbT4.pgp
Description: PGP signature

Re: editors/vim installs to /

[Lars Engels]

On Fri, Sep 17, 2010 at 05:38:21PM -0700, Rob Farmer wrote:
> On Fri, Sep 17, 2010 at 16:24, Wesley Shields  wrote:
> > On Fri, Sep 17, 2010 at 03:51:42PM -0700, Rob Farmer wrote:
> >> On Fri, Sep 17, 2010 at 13:54, Wesley Shields  wrote:
> >> > While I agree that editors/vim could use the changes you're discussing,
> >> > do you really think such a comment is needed? Attacks like that are not
> >> > necessary. Let your code speak for itself.
> >> >
> >> > -- WXS
> >>
> >> This port has major issues and numerous polite requests (including
> >> with patches) to fix them have been summarily ignored or rejected. So
> >> don't act surprised when people start to get annoyed by the situation.
> >
> > I'm not surprised. I'm pointing out that attacks like that are not going
> > to further the cause of getting the port the care you think it deserves.
> >
> > Unfortunately I don't know what the answer is beyond polite requests and
> > patches to fix the problems as you see them. I do know that attacks are
> > not the answer and are in fact harmful to achieving a goal.
> >
> > -- WXS
> >
> 
> Fair enough. My apologies if my comments on this were too aggressive.
> 
> However, I still think it would benefit everyone if the maintainer
> could provide an explanation for some of the current behavior and
> would at least be open to discussion about changing it. The biggest
> problem here, IMHO, is not the OPTIONS issue, but rather the use of
> GTK 1 as the default. Plenty of ports don't support OPTIONS, even
> though they could, and many users ignore options by setting BATCH, but
> it isn't a big deal because the defaults are ideal for most
> situations. I think either defaulting to GTK 2 or just making vim a
> console application would eliminate most of these complaints.

editors/vim-lite is console only.


pgpOCj7bxYWZn.pgp
Description: PGP signature

Re: Web feed for /usr/ports/UPDATING

[Lars Engels]

On Fri, Sep 24, 2010 at 01:39:25PM +1000, Alexander Kojevnikov wrote:
> Hi list,
> 
> Since the only SUBJ I could find [0] is long since dead I created my own:
> 
> http://updating.versia.com/
> 
> Any feedback is welcome.
> 
> Cheers,
> Alex
> 
> [0] http://lists.freebsd.org/mailman/htdig/freebsd-ports/2005-June/024285.html

Thank you! I like the Atom feed. :)


Lars


pgpHLBVZFTteN.pgp
Description: PGP signature

Re: Linux compatibility with more than one Linux installed?

[Lars Engels]

On Tue, Nov 29, 2011 at 03:27:15PM +0100, Alexander Leidinger wrote:
> Hi,
> 
> you can install the gentoo linux-dist in parallel to the default
> linux-base. Gentoo will be in /usr/local, not in /compat/linux. As
> such you have to manually start programs there via chroot. This means
> you do not have access to you FreeBSD files like normally, except you
> do null-mounts into the gentoo area. It also means your experience
> will not be as "integrated" as with the defaut linux-base (the
> linux-base port does some effort to integrate FreeBSD config files and
> installed resources like fonts).
> 
> Just switching between them, like changing a symlink, is theoretically
> possible, but the gentoo linux-dist port is not designed for this kind
> of integration. It's a linux-"dist" port, not a linux-"base" port.

What is it good for, then?


pgpSpG6dLkLPw.pgp
Description: PGP signature

Re: FreeBSD Port: linux_base-f10-10_4

[Lars Engels]

On Fri, Mar 09, 2012 at 01:44:25PM +0100, Alexander Leidinger wrote:
> Quoting Barry Tigner  (from Thu, 08 Mar 2012 12:16:27 -0500):
> 
> > eagle: /lib/libc.so.6: version `GLIBC_2.10' not found (required by
> > eagle)
> >
> > I can run version 5.1 in the meantime. But it looks like I will need
> > an updated version of linux_base-f10, perhaps an f11, f12 or f13 or f14
> > version.
> >
> > Are there plans to update linux_base-f10 sometime this year ?
> 
> Those which have the knowledge to produce a more recent linux_base  
> port, don't seem to have the time to do this. Those which tell to have  
> time and express interest to do this, seem to lose interest or time  
> when they get get aware of what needs to be done (see  
> http://www.leidinger.net/blog/2011/08/29/howto-create-a-new-linux_base-port/  
> and  
> http://www.leidinger.net/blog/2011/09/01/howto-add-linux-infrastructure-ports-for-a-new-linux_base-port/)
> 
> Or in short: we are aware that we need something more recent since a  
> long time, but there are no plans. Volunteers welcome.

Maybe this is something the foundation can sponsor?


pgpvt4MVH46rZ.pgp
Description: PGP signature

Re: [HEADSUP] pkgng 1.0-beta9 please test

[Lars Engels]

On Fri, Mar 30, 2012 at 11:12:42AM +0200, Baptiste Daroussin wrote:
> Hi,
> 
> On behalf of pkgng crew, I'm happy to announce pkg 1.0-beta9
>

[...]
 
> Please note that normally this will be the last beta version,

So we can expect an official package repository with the first RC?


pgppiqvK9yYVo.pgp
Description: PGP signature

Re: Proper way to detect kernel / userland sources?

[Lars Engels]

On Tue, Nov 09, 2010 at 11:38:22PM +0300, Dmitry Marakasov wrote:
> * Lev Serebryakov (l...@freebsd.org) wrote:
> 
> >   I'm  preparing port which depends both on kernel source (it contains
> > kernel module) and userland sources (it needs GEOM sources).
> > 
> >   I   see,   that  ports  with  kernel  modules  check  for  hardcoded
> >   "/usr/src/sys/Makefile".  But it doesn't look good: sources could be
> >   perfectly valid, but placed in other directory!
> > 
> >   Is  here  any  standerd  variable  which  should  be used instead of
> >   hardcoded "/usr/src"?

[...]

> While here, I'm worried about the fact that /usr/src is used as a
> possible source for OSVERSION. Currently, in presence of freebsd-update,
> it's really likely that system sources are out-of sync with installed
> system, so getting OSVERSION from /usr/src should likely be removed.
> osreldate is enough fallback if /usr/include/sys/param.h is absent
> for some reason.

AFAIK freebsd-update also updates /usr/src if /usr/src is not empty.


pgpNxVYW0p28V.pgp
Description: PGP signature

Re: Mk/bsd.command.mk: missing CSH tag

[Lars Engels]

On Fri, Nov 19, 2010 at 08:21:31PM +0300, Eir Nym wrote:
> On 19 November 2010 18:32, Christian Weisgerber  wrote:
> > Eir Nym  wrote:
> >
> >> >>> Since when? If you are missing /bin/csh, your system is defective
> >> >>> or at least nonstandard.
> >> >>
> >> >> It is good joke, thanks
> >> >
> >> > I guess he's talking about the ports tree being too fragile for some
> >> > non-default configurations and not many people are willing to fix it.
> >>
> >> I understand this. Port can check this (because it is optional system
> >> component) and use another or generate error.
> >
> > This is very confusing.  One of us is out of sync with reality.
> > (If it's me, I'd like to know.)  Your confident claim that csh is
> > optional is like stating that the sky is green and the sun is purple.
> >
> > Did I miss something?
> 
> If you think that any part of base system is mandatory, you should
> write request to remove knob WITHOUT_TCSH and any other, which you
> think is not optional.

If you want support from the FreeBSD community, every part of the base
system is mandatory.


pgpVDOqdK4AZu.pgp
Description: PGP signature

Re: packages compressed with xz

[Lars Engels]

On Sat, Dec 04, 2010 at 11:19:21PM +0100, Simon L. B. Nielsen wrote:
> 
> On 30 Nov 2010, at 03:16, jhell wrote:
> 
> > Agreed. Soon can be quantified by actual need and of which there is not
> > much need except for larger packages but adding this would just add
> > unneeded complication to the system that is already in place.
> 
> 
> We are running out of diskspace on event the FTP master site -
> currently we are at ~1TB. The xz compression gives as significant
> space saving - so there is already a need.
> 
> PS. anyone saying a 1 TB etc. disk is cheap will be ignored.

And all ftp mirror admins will be very grateful to sync smaller
.xz packages. :)


pgpADHhbR7zTC.pgp
Description: PGP signature

Re: making all ports in /usr/ports on FreeBSD 8.1

[Lars Engels]

On Sat, Dec 11, 2010 at 01:29:05AM -0800, Norm Larkin wrote:
> Hello,
> 
> I was idly trying to experiment and decided I wanted to see how long it took, 
> how much disk space was involved, how hard it was on a system, and so on, to 
> build the entire ports tree.  I loaded up a fresh system with FreeBSD 8.1R on 
> i386, used all defaults for the installer options, had it install all sources 
> and the ports tree, went into /usr/ports, set BATCH to yes, and did "make 
> install".  It bombed within about an hour.  Figuring my ports were out of 
> date, 
> I repeated this after wiping all of /usr/local, /var/db/pkg, /usr/ports, and 
> then using portsnap to fetch and install.  Same result.  I then tried loading 
> the amd64 version.  Same thing.
> 
> What am I doing dumb here (other than possibly trying to build all ports).  
> It 
> seems to always get messed up on libxml2.

Have you tried building libxml2 only?


pgpJqIFoUilXd.pgp
Description: PGP signature

Re: portmaster: print /usr/ports/UPDATING on update

[Lars Engels]

On Tue, Dec 28, 2010 at 10:59:04AM -0800, Doug Barton wrote:
> On 12/27/2010 23:07, Eygene Ryabinkin wrote:
> > I had shown the simple shell script that will parse the UPDATING and
> > present the entries for the given port if the fall into the "last N
> > days" category.  If you had missed it -- ping me, I'll show it to you
> > once again.
> 
> Did you even read my post? I specifically stated that I had caught up 
> with the thread (which implies that I saw your script). I also said that 
> trying to write a parser for the UPDATING text file is a bad idea, and 
> not something I'm interested in pursuing. I was taking pains to avoid 
> having to specifically delineate all the reasons your suggestion is a 
> bad idea because I'd rather focus on moving in a more useful direction.

Picking a random mail from this thread...

Is anyone aware of pkg_updating(1)? It's in base for 2 years.


pgpXuljXj6AuL.pgp
Description: PGP signature

Re: How do I trace which ports call for a specific lib?

[Lars Engels]

On Mon, Jan 03, 2011 at 10:56:59AM +, David Southwell wrote:
> Due to problems with apache22 running using ssl from ports I have deinstalled 
> ssl from ports and recompiled a number which I know used libssl.so.7.
> 
> I still keep finding ports needing libssl.so.7 which need to be recompiled to 
> use the standard OS library.
> 
> How do I identify the remaining ports I need to rebuild?
> 
> Thanks in advance

pkg_libcheck from sysutils/bsdadminscripts


pgpks2lKkpvhz.pgp
Description: PGP signature

Re: FreeBSD ports which are currently marked broken

[Lars Engels]

On Fri, Jan 07, 2011 at 11:34:05AM +, Anton Shterenlikht wrote:
> On Fri, Jan 07, 2011 at 08:29:10AM +0100, lini...@freebsd.org wrote:
> > 
> > portname:   math/dislin
> > broken because: size mismatch
> > build errors:   none.
> > overview:   
> > http://portsmon.FreeBSD.org/portoverview.py?category=math&portname=dislin
> > 
> 
> Is this a security concern?
> I've never used this port before, but it looks intersting.
> 
> By doing
> 
> rm distinfo*
> make makesum
> 
> I can install this port. Is this not a good idea?

No, it is not. You must check, why the distfile has a different
checksum. It may be because there was a back door inserted.


pgpSxoGoyf5zA.pgp
Description: PGP signature

Re: LIRC - Linux Infared Remote Control

[Lars Engels]

On Thu, Feb 17, 2011 at 08:22:23PM -0500, grarpamp wrote:
> Putting 'infrared' into the search box here:
>  http://www.freebsd.org/ports/
> fails to list this port, because its description is spelled wrong.
> Daniel no longer maintains this. So I suppose the listing, long
> description, and Makefile contacts should be cut over to ports@.
> Thanks.

Probably nox@ should step up? :)


pgpnNi052IjxS.pgp
Description: PGP signature

Re: [HEADS UP] Ports Infrastructure Changes

[Lars Engels]

On Sat, Mar 19, 2011 at 09:49:39AM +0800, Martin Wilke wrote:
> Hey,
> 
> as the Ports Collection continue to grow, we have decided to
> do some changes to the category layout. The www category, second
> largest with over 2000 individual ports, will have three subcategories
> spinned out. On the other side, x11-servers category, with only
> 10 ports, will be folded into regular x11 category.
> 
> Attached is a proposed list of ports being moved from the www category.
> Please review, discuss and report ommissions and mistakes. The general
> key to the new categories is as follows:
> 
> www-clients - browsers, rss clients, wget-alike, webapi/soap clients,
> benchmarks
> www-servers - http servers, proxy servers, everything related to apache
> www-webapps - web apps, frameworks, libraries
> www (rest, not moved) - html editors, authoring tools, search engines ..

Shouldn't we move html editors to ports/editors?


pgpV9XneXJQzr.pgp
Description: PGP signature

Re: Propose new macro: INSTALL_CONF

[Lars Engels]

On Sat, May 14, 2011 at 01:05:33PM -0500, Stephen Montgomery-Smith wrote:
> Chris Rees wrote:
> > Hi all,
> >
> > I'm getting frustrated with editing config files of ports in vi, and
> > being told it's read-only.
> >
> > This stops me using ZZ to quit, which makes me sad.
> >
> I do :w!:q which is only three key strokes longer than ZZ.
> 
> (My apologies if I am missing something.)

On a German keyboard that is:

Shift + .
w
Shift + 1
Shift + .
q
Enter

9 Keystrokes

vs.

Shift + ZZ

3 Keystrokes




pgpKIh9cjGUUJ.pgp
Description: PGP signature

Re: Small question about FreeNX for freebsd.

[Lars Engels]

On Thu, Nov 29, 2007 at 09:48:20AM -0500, dewey hylton wrote:
> Quoting Mathias Picker <[EMAIL PROTECTED]>:
> 
> > It's for the port I got from your website. Might be some time since I
> > unpacked it.
> 
> okay, i'll try that first and then see if i can't make the patch fit the newer
> sources as well. thanks again!

Dewey,

did you have any success so far?

Lars


pgpdGzlJLi3tu.pgp
Description: PGP signature

Re: [ GSOC ] Differences in shell behaviour

[Lars Engels]

On Fri, Jun 01, 2012 at 09:38:38AM +0400, Alexander Pyhalov wrote:
> Good morning.
> 
> On 06/01/2012 07:53, Jason Hellenthal wrote:
> >
> >
> > On Thu, May 31, 2012 at 11:21:10PM +0400, Alexander Pronin wrote:
> >> The problem is:
> >> ### sh in 8.3
> >> $ false&  pid=$!
> >> $
> >> [1]   Done (1)false
> >> $ wait ${pid}
> >> wait: No such job: 4852
> >
> > I don't see this behavior on 8.3-STABLE @r236350 i386
> >   ---
> > Console>  false&  pid=$!
> > Console>  wait ${pid}
> > [1]   Done (1)false
> > Console>  echo $?
> > 1
> 
> It seems to behave differently, when you issue some additional commands 
> or interact with shell.
> 
> first case (8.3 r234443):
> $ false &pid=$!
> $ wait ${pid}
> [1]   Done (1)false
> $ echo $?
> 1
> 
> second case (8.3 r234443):
> $ false & pid=$!
> $ # some interaction with shell
> [1]   Done (1)false
> $ wait ${pid}
> wait: No such job: 59092
> 
> 
> Now, on 9.0-RELEASE
> first case:
> $ false & pid=$!
> $ wait ${pid}
> [1]   Done(1) false
> $ echo $?
> 1
> 
> second case:
> $ false & pid=$!
> $ # some activity
> [1]   Done(1) false
> $ wait ${pid}
> $ echo $?
> 1
> 
> Do you see the difference ? Which behavior is correct? Can it be a sh bug?
> 

Adding jilles to CC, he worked on sh(1) during the last months.


pgpPbzyffKaQE.pgp
Description: PGP signature

[OPTIONS NG] multiple OPTIONS_MULTI not possible

[Lars Engels]

Hi all,

I think I found a bug in the new Options framework:

When more than one MULTI group is defined, only the last one is shown
in the OPTIONS window and in "make showconfig":

# make showconfig
===> The following configuration options are available for atunes-2.0.1_2:
 CDDA2WAV=on: Ripper:  Enable cdrtools support
> Options available for the multi ENGINE: you have to choose at least one 
of them
 MPLAYER=on: Engine:  Use Mplayer
 XINE=off: Engine:  Use Xine
===> Use 'make config' to modify these settings

The port's Makefile looks like this:

[...]

OPTIONS_DEFINE= CDDA2WAV

OPTIONS_MULTI=  ENCODER
OPTIONS_MULTI_ENCODER=  LAME VORBIS FLAC

OPTIONS_MULTI=  ENGINE
OPTIONS_MULTI_ENGINE=   MPLAYER XINE

OPTIONS_DEFAULT=MPLAYER CDDA2WAV LAME VORBIS

MPLAYER_DESC=   Engine:  Use Mplayer
XINE_DESC=  Engine:  Use Xine
CDDA2WAV_DESC=  Ripper:  Enable cdrtools support
LAME_DESC=  Encoder: Enable lame MP3 encoder
VORBIS_DESC=Encoder: Enable vorbis OGG encoder
FLAC_DESC=  Encoder: Enable FLAC encoder

.include 

[...]

So the ENCODER MULTI selection is missing.

Lars  


pgp0akeqa6j5k.pgp
Description: PGP signature

Re: [OPTIONS NG] multiple OPTIONS_MULTI not possible

[Lars Engels]

On Mon, Jun 04, 2012 at 09:41:40PM +0100, Matthew Seaman wrote:
> On 04/06/2012 21:29, Lars Engels wrote:
> > OPTIONS_DEFINE= CDDA2WAV
> > 
> > OPTIONS_MULTI=  ENCODER
> > OPTIONS_MULTI_ENCODER=  LAME VORBIS FLAC
> > 
> > OPTIONS_MULTI=  ENGINE
> > OPTIONS_MULTI_ENGINE=   MPLAYER XINE
> > 
> > OPTIONS_DEFAULT=MPLAYER CDDA2WAV LAME VORBIS
> 
> You need:
> 
> OPTIONS_MULTI=ENCODER ENGINE
> OPTIONS_MULTI_ENCODER=LAME VORBIS FLAC
> OPTIONS_MULTI_ENGINE= MPLAYER XINE
> 

Thanks Matthew,

the PH should be a bit clearer here. :)

Lars


pgpU2V9xKGl4L.pgp
Description: PGP signature

Re: libpng.so.6 missing

[Lars Engels]

On Mon, Jun 11, 2012 at 10:07:22PM -0700, Waitman Gobble wrote:
> Warren Block  wrote ..
> > On Mon, 11 Jun 2012, Waitman Gobble wrote:
> > 
> > > I ran pkg_libchk and it looks like a whole boatload of packages need 
> > > to be replaced, so I decided to skip to the chase and give the update 
> > > script a 'replace' option.. it checks the package version available in 
> > > the packages directory on the freebsd site with what's installed, if 
> > > there's a newer version it downloads it and does the MD5 check, 
> > > creates an update.sh script to replace (the update script doesn't 
> > > actually do any udpating!) Anyhow, with 'replace' it will either 
> > > replace the existing or use the newer if available. I've been using 
> > > this script to update the system and it works pretty good for me, 
> > > except when I veer off path and get into ports like with my libpng 
> > > issue. :)
> > 
> > There is a pkg_upgrade command in the bsdadminscripts, too.  However, 
> > pkgng will change all that soon.
> 
> Thanks, I tried pkgng a few months ago and it didn't seem to do
> updates... but I recall many updates on the mail list so I'm sure it's
> much different now, and works much better. I'll definitely check it
> out.

It does, but you need a working repository for it.


pgp4qAIwWWtGS.pgp
Description: PGP signature

Re: libpng.so.6 missing

[Lars Engels]

On Mon, Jun 11, 2012 at 11:06:46PM -0700, Waitman Gobble wrote:
> Lars Engels  wrote ..
> > On Mon, Jun 11, 2012 at 10:07:22PM -0700, Waitman Gobble wrote:
> > > Warren Block  wrote ..
> > > > On Mon, 11 Jun 2012, Waitman Gobble wrote:
> > > > 
> > > > > I ran pkg_libchk and it looks like a whole boatload of packages need 
> > > > > to be replaced, so I decided to skip to the chase and give the update 
> > > > > script a 'replace' option.. it checks the package version available 
> > > > > in 
> > > > > the packages directory on the freebsd site with what's installed, if 
> > > > > there's a newer version it downloads it and does the MD5 check, 
> > > > > creates an update.sh script to replace (the update script doesn't 
> > > > > actually do any udpating!) Anyhow, with 'replace' it will either 
> > > > > replace the existing or use the newer if available. I've been using 
> > > > > this script to update the system and it works pretty good for me, 
> > > > > except when I veer off path and get into ports like with my libpng 
> > > > > issue. :)
> > > > 
> > > > There is a pkg_upgrade command in the bsdadminscripts, too.  However, 
> > > > pkgng will change all that soon.
> > > 
> > > Thanks, I tried pkgng a few months ago and it didn't seem to do
> > > updates... but I recall many updates on the mail list so I'm sure it's
> > > much different now, and works much better. I'll definitely check it
> > > out.
> > 
> > It does, but you need a working repository for it.
> 
> I update ports in my sup file, along with the FreeBSD source. I
> normally csup at least every two weeks. Is this what you mean by
> working ports repository?
> 
> I previously ran into a snag if the package version was different than
> the ports version, and it seems occasionally packages lag a bit.

No, you need a package repository for pkgng, not the ports tree.
You can try 
# setenv PACKAGESITE "http://pkgbeta.freebsd.org/`uname|tr '[:upper:]' 
'[:lower:]'`-`uname -r|cut -d. -f1`-` uname -m`/latest"
# pkg update
# pkg upgrade

But please take note because pkg can also downgrade a package if
the remote repository has an older version that the one that you have
installed.



pgpSmzpvhnWnk.pgp
Description: PGP signature

Re: libpng.so.6 missing

[Lars Engels]

On Tue, Jun 12, 2012 at 12:31:29AM -0700, Waitman Gobble wrote:
> Lars Engels  wrote ..
> > On Mon, Jun 11, 2012 at 11:06:46PM -0700, Waitman Gobble wrote:
> > > Lars Engels  wrote ..
> > > > On Mon, Jun 11, 2012 at 10:07:22PM -0700, Waitman Gobble wrote:
> > > > > Warren Block  wrote ..
> > > > > > On Mon, 11 Jun 2012, Waitman Gobble wrote:
> > > > > > 
> > > > > > > I ran pkg_libchk and it looks like a whole boatload of packages 
> > > > > > > need
> > > > > > > to be replaced, so I decided to skip to the chase and give the 
> > > > > > > update
> > > > > > > script a 'replace' option.. it checks the package version 
> > > > > > > available in
> > > > > > > the packages directory on the freebsd site with what's installed, 
> > > > > > > if
> > > > > > > there's a newer version it downloads it and does the MD5 check, 
> > > > > > > creates an update.sh script to replace (the update script doesn't 
> > > > > > > actually do any udpating!) Anyhow, with 'replace' it will either 
> > > > > > > replace the existing or use the newer if available. I've been 
> > > > > > > using 
> > > > > > > this script to update the system and it works pretty good for me, 
> > > > > > > except when I veer off path and get into ports like with my 
> > > > > > > libpng 
> > > > > > > issue. :)
> > > > > > 
> > > > > > There is a pkg_upgrade command in the bsdadminscripts, too.  
> > > > > > However, 
> > > > > > pkgng will change all that soon.
> > > > > 
> > > > > Thanks, I tried pkgng a few months ago and it didn't seem to do
> > > > > updates... but I recall many updates on the mail list so I'm sure it's
> > > > > much different now, and works much better. I'll definitely check it
> > > > > out.
> > > > 
> > > > It does, but you need a working repository for it.
> > > 
> > > I update ports in my sup file, along with the FreeBSD source. I
> > > normally csup at least every two weeks. Is this what you mean by
> > > working ports repository?
> > > 
> > > I previously ran into a snag if the package version was different than
> > > the ports version, and it seems occasionally packages lag a bit.
> > 
> > No, you need a package repository for pkgng, not the ports tree.
> > You can try 
> > # setenv PACKAGESITE "http://pkgbeta.freebsd.org/`uname|tr '[:upper:]' 
> > '[:lower:]'`-`uname
> > -r|cut -d. -f1`-` uname -m`/latest"
> > # pkg update
> > # pkg upgrade
> > 
> > But please take note because pkg can also downgrade a package if
> > the remote repository has an older version that the one that you have
> > installed.
> 
> Thanks so much for the info. Do you have an idea about how long it would take 
> to replace 700 packages?

Much faster than using ports! ;-)
I can't tell, it depends on your internet connection, pkgbeta's current
bandwidth, etc. But apart from the download it should be pretty fast.
Extracting the txz and updating the sqlite database is faster than
extracting the tbz and updating /var/db/pkg/*


pgpL4bxMd5M1a.pgp
Description: PGP signature

Re: maintainer timeout for FreeBSD commiters

[Lars Engels]

On Tue, Jul 17, 2012 at 05:43:02PM -0500, Mark Linimon wrote:
> On Wed, Jul 18, 2012 at 12:09:50AM +0200, John Marino wrote:
> > Would it be so bad if all my submitted patches (as a recognized
> > quality contributor with history) just got committed as a passthrough?
> 
> This has been explored on the mailing lists before, however, we don't
> technically have a way to do either of the following:
> 
>  - let people commit to "just some" ports

Shouldn't this work with subversion?


pgpstPXYxNAYD.pgp
Description: PGP signature

Re: cvs commit: ports/x11/slim Makefile pkg-plist ports/x11/slim/files pam.conf slim.sh.in

[Lars Engels]

On Mon, Jul 30, 2012 at 01:37:45PM +0400, Eygene Ryabinkin wrote:
> Wed, Jul 18, 2012 at 08:37:30AM +0400, Eygene Ryabinkin wrote:
> > Thu, Jul 12, 2012 at 12:26:15AM -0400, Henry Hu wrote:
> > > For the png problem, I think that we can use png_jmpbuf for any
> > > libpng
> > > >= 1.2.5? It seems to be exist at least from libpng 1.2.5
> > > (http://www.libpng.org/pub/png/libpng-1.2.5-manual.html) so it's
> > > safe to use it?
> > 
> > Should be.  But according to the portability note at
> >   http://www.libpng.org/pub/png/libpng.html
> > "The libpng 1.5.x series continues the evolution of the libpng API,
> > finally hiding the contents of the venerable and hoary png_struct and
> > png_info data structures inside private (i.e., non-installed) header
> > files."  So it is normal to use the "new" API only for >= 1.5.x.
> > 
> > Mon, Jul 16, 2012 at 01:07:06AM -0700, Doug Barton wrote:
> > > Where are we at with this? I'm using the latest png with your patch and
> > > it is working fine, although only a few of my backgrounds are PNGs.
> > 
> > I had tested it with PNG 1.4.10 -- works fine.  So, I had changed
> > the required library version for png from '15' to '1[45]'.  The patch
> > was modified accordingly,
> >   http://codelabs.ru/fbsd/ports/slim/upgrade-1.3.3-to-1.3.4.diff
> 

You mean 1.3.4 which is in the tree already? I'm using it without any
problems.
PAM works like a charm, no more need to start ssh-agent manually. :)


pgpj9sMKcxXId.pgp
Description: PGP signature

Re: P2 testing of pkg

[Lars Engels]

On Fri, Aug 24, 2012 at 07:16:48PM -0700, Jeffrey Bouquet wrote:
> pkg2ng fails to register anything:
> Undefined symbol "_ThreadRuneLocale"
> It tries; Each port is attempted to be registered.
> ...
> Unknown if that is because of the p2 having an earlier version
> of 9-STABLE than upon which was built /pkg/
> ...
> As an aside, now that bsdstats.org has its port statistics back up,
> I see that /pkg/ is installed in only a small subset of reporting
> BSD/pc-bsd/etc/ machines... 
> portupgrade   4697
> portmaster2039
> portmanager322
> portupgrade-devel  185
> pkg 41
> As of earlier today anyway.

That's because PC-BSD has portupgrade installed and bsdstats activeated
by default. 
I guess only a few people are still running bsdstats, because it was
broken for so long...


pgp5GXYw3nYkn.pgp
Description: PGP signature

Re: Clang as default compiler November 4th

[Lars Engels]

On Mon, Sep 10, 2012 at 10:54:04PM -0700, Doug Barton wrote:
> As of last week, 4,680 ports out of 23,857 failed to build with clang on
> 9-amd64. That's almost a 20% failure rate. Until we have better support
> for either building ports with clang, or have better support for the
> idea of a "ports compiler," this change is premature. The ports are an
> important part of the FreeBSD Operating _System_, and pulling the
> trigger on the default compiler before the ports problems are addressed
> robustly seems like a big fat FU.
> 
> That said, I agree that this issue needs to be addressed. In fact, 9
> months before the release of 9.0 I said on the internal committers list
> that there was no point in making a new release until we had thoroughly
> addressed both the default compiler for the base, and resolving the
> "ports compiler" issue. While there has been some movement on the
> former, there has been nothing done on the latter for years now, even
> though everyone agrees that it is an important issue.
> 
> I'd like to request that rather than moving the default compiler
> prematurely that you call for volunteers to address the problems with
> the ports. Both the issues of fixing more ports to build correctly with
> clang, and the issue of defining a "ports compiler" version of gcc (and
> appropriate infrastructure) for those that can't. Once those issues are
> resolved there would not be any further obstacles to moving the default.
> Until they are, the change is premature.
> 
> Doug

Doug, as you can already use CLANG instead of GCC now, you will be able
to use GCC instead of CLANG after November 4th.

At the moment the ports maintainers don't give much about if their ports
build with CLANG or not because they're not forced to.
Those who don't run CURRENT won't notice, but those who do will have to
get their butts up and fix the ports, so 10.0 can have 99% of all ports
build with CLANG and even 8.x and 9.x can already profit from having the
broken ports fixed now.


pgpFIV5jKkyQL.pgp
Description: PGP signature

Re: Clang as default compiler November 4th

[Lars Engels]

On Wed, Sep 12, 2012 at 04:15:20AM -0500, Mark Linimon wrote:
> On Tue, Sep 11, 2012 at 11:27:50AM +0200, Lars Engels wrote:
> > At the moment the ports maintainers don't give much about if their ports
> > build with CLANG or not because they're not forced to.
> 
> I think this is a mis-representation.
> 
> Adding the requirement "your ports must work on clang" is adding an
> ex-post-facto requirement.  This creates the following matrix of what
> we are implicitly asking maintainers to do:
> 
> (FreeBSD 7|8|9|10) * (amd64|arm|i386|powerpc|sparc64) * (base gcc|base clang)
> 
> It is completely insane to expect anyone to be able to test in all of those
> environments, or even a tiny subset of them.  This isn't what most people
> sign up for when they sign up to maintain ports.

No, I didn't mean it that way. I only meant that the people /
maintainers running CURRENT will actually see that their ports don't
work and if they want to keep on using them on CURRENT they need to fix
them. e.g. two of the ports I maintain don't build with CLANG, yet. I
just checked that on the wiki page [1].
I had to look that up manually, but would have experienced that if I my
CURRENT box was building with CLANG by default. :)

It's clear that we cannot expect our maintainers to check all possible
combinations of FreeBSD, architecture and compiler.

> 
> > Those who don't run CURRENT won't notice, but those who do will have to
> > get their butts up and fix the ports
> 
> I think it's foolish to assume that maintainres don't have their butts in
> gear as it is.  Please note, we have nearly 1300 PRs, hundreds of ports with
> build errors and/or PRs, and hundreds that fail on -current only.  I try to
> advertise all these things the best I know how.  Adding the hundreds that
> fail on -clang only and then blaming the maintainers is simply going to be
> counter-productive.



[1] http://wiki.freebsd.org/PortsAndClang


pgp2qfIiXlAlJ.pgp
Description: PGP signature

Re: redports: USA_RESIDENT=YES ?

[Lars Engels]

On Thu, Sep 27, 2012 at 04:36:34PM +0100, Chris Rees wrote:
> On 27 Sep 2012 16:29, "Anton Shterenlikht"  wrote:
> >
> > What is the meaning of USA_RESIDENT=YES in redports build logs?
> >
> 
> The US government considers cryptography a weapon, so exporting it is
> technically an offence.  Therefore, a declaration that you're a US resident
> is required for strong cryptography, since the rest of the world is full of
> terrorists and whatnot.

Is that still so? IIRC that is no longer true since a few years.


pgpI1gp8umAFu.pgp
Description: PGP signature

Re: Steam, linux version

[Lars Engels]

On Wed, Nov 07, 2012 at 11:01:40PM +0100, Alexander Leidinger wrote:
> On Wed, 07 Nov 2012 10:46:43 -0800 Mike Carlson 
> wrote:
> 
> > On 11/7/2012 1:44 AM, Alexander Yerenkow wrote:
> > > Hey guys.
> > > Steam is now in Beta for Ubuntu, they provide *.deb file.
> > >
> > > Do someone working on bringing it to FreeBSD with linux
> > > emulation? :)
> > >
> > >
> > That would be fantastic to have!
> 
> I would expect that you may only get something up and running with the
> highly experimental and incomplete (it's not rocked science, I have a
> blog post about adding what's missing) linux_base-c6... if at all.
> I would expect that it depends upon a more recent glibc than what we
> have on the default linux_base port.

What's the current state of linux_base-c6? Will it hit the ports tree
after 9.1? You latest blog post [1] is from May, so maybe something
happened in the meantime?

[1] http://www.leidinger.net/blog/2012/05/18/linux_base-c6/


Lars


pgpgBaSf3hmns.pgp
Description: PGP signature

Re: fixing missing launch icons

[Lars Engels]

On Fri, Nov 09, 2012 at 01:49:22PM +, Olivier Duchateau wrote:
> 2012/11/9 Beeblebrox :
> > Some ports fail to create the launch icon (menu item) in the desktop menu. 
> > To
> > correct this, one is to add in /usr/local/share/application a file by
> > .desktop like so:
> >
> > [Desktop Entry]
> > Encoding=UTF-8
> > Name=
> > GenericName=
> > Comment=
> > TryExec=
> > Exec=
> > Icon=
> > Type=Application
> > Categories=;;;
> >
> > My question is: The menu entries have categories - for example in gnome
> > there are Graphics, Office, Internet, etc. How can one specify the category
> > placement (under which category) this icon should go?
> >
> 
> There's specification [1] for create (and understand) desktop menu.
> 
> About icons, usually, we can find in /usr/local/share/icons and
> /usr/local/share/pixmaps directories.
> 
> Note: some ports don't provide .desktop file, it's not necessarily "bug".

But for desktop applications port maintainers should create one:
http://www.freebsd.org/doc/en/books/porters-handbook/book.html#desktop-entries


pgpW0c04RyBOv.pgp
Description: PGP signature

Re: issue with sudo-1.8.23

[Lars Engels]

On Fri, May 04, 2018 at 07:56:10AM +0200, Lars Engels wrote:
> On Thu, May 03, 2018 at 09:15:14PM +0200, Walter Schwarzenfeld wrote:
> > In this version /var/run/sudo is changed to /run/sudo. If /var/run/sudo 
> > in the pkg-plist causes the problem if a directory /run exists.
> > 
> > But solved, fixed by maintainer.
> 
> Can we please revert this to /var/run?
> /run is some canker coming from systemd
> http://www.h-online.com/open/news/item/Linux-distributions-to-include-run-directory-1219006.htm.

Correction:

http://www.h-online.com/open/news/item/Linux-distributions-to-include-run-directory-1219006.html


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Upgrade from PHP71 to PHP72 breaks icingaweb2

[Lars Engels]

On Wed, Nov 07, 2018 at 08:48:19AM +0100, Guido Falsi wrote:
> On 07/11/18 08:46, Guido Falsi wrote:
> > On 07/11/18 07:24, Xavier wrote:
> >> On 03/11/2018 18:50, Guido Falsi wrote:
> >>> On 03/11/18 18:17, Xavier Humbert wrote:
>  Context FreeBSD 11-STABLE, last pkg upgrade led to update PHP71 to PHP72.
>  php72-json is installed, but when I launch a navigator, IcingaWeb2
>  crashes with :
> 
> > Call to undefined function Icinga\Util\json_encode() in
> > /usr/local/www/icingaweb2/library/Icinga/Util/Json.php:57
> >
> 
>  Any idea ?
> >>>
> >>> Yess, you need to install the php72-json package which provides the
> >>> json_encode() function.
> >>>
> >>> The port actually depends on it, so something went wrong with your update.
> >>>
> >>> You should try reinstalling it and check that all dependencies install
> >>> successfully.
> >>>
> >>
> >> Thanks for your answer Guido. Unfortunately, as I wrote, php-json *is*
> >> installed, in the correct flavour. And pkg check -Bd succeeds
> >>
> > 
> > Is it being loaded?
> > 
> > Check for 'ext-20-json.ini' to be present in /usr/local/etc/php and have
> > correct content.
> > 
> 
> BTW, if you've not tried it a 'pkg install -f php72-json' is worth a try.

Can you check if you also upgraded the mod_php[57][16] module for
Apache?
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Upgrade from PHP71 to PHP72 breaks icingaweb2

[Lars Engels]

On Thu, Nov 08, 2018 at 01:02:43PM +0100, Xavier wrote:
> On 08/11/2018 12:57, Xavier wrote:
> > On 07/11/2018 13:09, Lars Engels wrote:
> >> On Wed, Nov 07, 2018 at 08:48:19AM +0100, Guido Falsi wrote:
> >>> On 07/11/18 08:46, Guido Falsi wrote:
> >>>> On 07/11/18 07:24, Xavier wrote:
> >>>>> On 03/11/2018 18:50, Guido Falsi wrote:
> >>>>>> On 03/11/18 18:17, Xavier Humbert wrote:
> >>>>>>> Context FreeBSD 11-STABLE, last pkg upgrade led to update PHP71 to 
> >>>>>>> PHP72.
> >>>>>>> php72-json is installed, but when I launch a navigator, IcingaWeb2
> >>>>>>> crashes with :
> >>>>>>>
> >>>>>>>> Call to undefined function Icinga\Util\json_encode() in
> >>>>>>>> /usr/local/www/icingaweb2/library/Icinga/Util/Json.php:57
> >>>>>>>>
> >>>>>>>
> >>>>>>> Any idea ?
> >>>>>>
> >>>>>> Yess, you need to install the php72-json package which provides the
> >>>>>> json_encode() function.
> >>>>>>
> >>>>>> The port actually depends on it, so something went wrong with your 
> >>>>>> update.
> >>>>>>
> >>>>>> You should try reinstalling it and check that all dependencies install
> >>>>>> successfully.
> >>>>>>
> >>>>>
> >>>>> Thanks for your answer Guido. Unfortunately, as I wrote, php-json *is*
> >>>>> installed, in the correct flavour. And pkg check -Bd succeeds
> >>>>>
> >>>>
> >>>> Is it being loaded?
> >>>>
> >>>> Check for 'ext-20-json.ini' to be present in /usr/local/etc/php and have
> >>>> correct content.
> >>>>
> >>>
> >>> BTW, if you've not tried it a 'pkg install -f php72-json' is worth a try.
> >>
> >> Can you check if you also upgraded the mod_php[57][16] module for
> >> Apache?
> >>
> > 
> > Ah ! I tried already too reinstall php72-json, but not mod_php
> > And it fails :
> > 
> > # pkg install -f mod_php72
> > Updating FreeBSD repository catalogue...
> > FreeBSD repository is up to date.
> > All repositories are up to date.
> > The following 1 package(s) will be affected (of 0 checked):
> > 
> > New packages to be INSTALLED:
> > mod_php72: 7.2.11
> > 
> > Number of packages to be installed: 1
> > 
> > The process will require 5 MiB more space.
> > 1 MiB to be downloaded.
> > 
> > Proceed with this action? [y/N]: y
> > [1/1] Fetching mod_php72-7.2.11.txz: 100%1 MiB   1.2MB/s00:01
> > pkg: cached package mod_php72-7.2.11: size mismatch, fetching from remote
> > Fetching mod_php72-7.2.11.txz: 100%1 MiB   1.2MB/s00:01
> > pkg: cached package mod_php72-7.2.11: size mismatch, cannot continue
> > 
> > I'll investigate that.
> > 
> > Thanks,
> > 
> 
> Well, after pkg update, it installs, but the web is still failing

Do you see any php related entries in your apache logs?
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Upgrade from PHP71 to PHP72 breaks icingaweb2

[Lars Engels]

On Thu, Nov 08, 2018 at 10:06:15PM +0100, Xavier wrote:
> On 08/11/2018 14:17, Lars Engels wrote:
> > Do you see any php related entries in your apache logs?
> > 
> 
> No, just the stack trace on screen
> 

I just encountered the same problem after upgrading from php71 to php72.
I had to also upgrade mod_php71 to mod_php72 and restart Apache
afterwards. Now Icinga Web 2 is up and running again.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: A potential new porter seeking some clarifications

[Lars Engels]

On Thu, Dec 13, 2018 at 10:41:01PM +0800, Arthur Pirika wrote:
> Hi all! I’m hoping to get into porting for FreeBSD, right now just
> focusing on one package, a plugin for bitlbee, however I’d like to
> extend my hand to maintain other ports in the future once I have more
> knowledge and practice with the system. 

Welcome! :-)
> 
> Before I start, though, I just need some clarifications of things from the 
> porter’s handbook. 
> 
> 1. If I understand correctly, the version of the ports tree as fetched
> by portsnap isn’t the best for working on the tree. I should instead
> make another copy of the tree as an svn checkout? Distfiles, however,
> still go to /usr/ports/distfiles

You can change this by setting DISTDIR variable in /etc/make.conf to a
directory you like. See ports(7) manpage.

> 2. Is it absolutely necessary to use poudriere before submitting a
> port? I’m still getting to grips with how it works, and if I need to
> get comfortable with it first, I’ll do so. 

That really depends on the change's size. Trivial patches can often be
sub-/committed without a poudriere run. portlint -ac, make check-plist
and make package can find potential issues for you.
Bigger changes should be build in poudriere. You don't need to attach
the logs to the PR, though.


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: vim - GTK2 or GTK3?

[Lars Engels]

On Tue, Jan 01, 2019 at 01:07:24PM -0700, Adam Weinberger wrote:
> I'm curious whether the default Vim port should use GTK2 or GTK3 as
> its UI toolkit, but I use neither so I need input from people here.
> 
> Right now it defaults to GTK2, but I'm suspecting that more people use
> GTK3 these days. I haven't run X in about 10 years, so I don't really
> know one way or the other. If anybody on this list has thoughts about
> GTK2 vs GTK3 (or something else!) as the default, I'd love to hear it.
> 
> The Vim choices are currently a mess, but it'll get better once
> subpackages land.

Firefox and Chromium both depend on GTK3, so it's highly likely that a
typical desktop user has GTK3 installed.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: net-mgmt/icingaweb2 fails to build with PHP 7.3

[Lars Engels]

On Sun, Jan 27, 2019 at 02:45:45PM +0100, Stefan Bethke wrote:
> It appears that (older?) versions of icingaweb2 do not work correctly with 
> PHP 7.3. From my poudriere build log:
> > ===>  Staging for icingaweb2-2.6.2_1
> > ===>   Generating temporary packing list
> > /bin/mkdir -p 
> > /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/stage/usr/local/share/examples/icingaweb2/bash_completion.d/
> > install  -m 0644 
> > /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/icingaweb2-2.6.2/etc/bash_completion.d/icingacli
> >   
> > /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/stage/usr/local/share/examples/icingaweb2/bash_completion.d
> > (cd /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/icingaweb2-2.6.2 && /bin/rm 
> > -f -r .mailmap changelog.py icingaweb2.spec  bin/license_writer.py packages 
> > test)
> > (/usr/bin/find /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/icingaweb2-2.6.2 
> > -name "*.bak" -delete)
> > /bin/mkdir -p 
> > /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/stage/usr/local/www/icingaweb2
> > (cd /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/icingaweb2-2.6.2 &&  
> > /bin/sh -c '(/usr/bin/find -Ed $1 $3 | /usr/bin/cpio -dumpl $2 >/dev/null 
> > 2>&1) &&  /usr/bin/find -Ed $1 $3 \(   -type d -exec /bin/sh -c '\''cd 
> > '\''$2'\'' && chmod 755 "$@"'\'' . {} +  -o -type f -exec /bin/sh -c '\''cd 
> > '\''$2'\'' && chmod 0644 "$@"'\'' . {} + \)' COPYTREE_SHARE . 
> > /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/stage/usr/local/www/icingaweb2)
> > /bin/chmod 755 
> > /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/stage/usr/local/www/icingaweb2/bin/icingacli
> > install -l rs 
> > /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/stage/usr/local/www/icingaweb2/bin/icingacli
> >  /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/stage/usr/local/bin/icingacli
> > /bin/mkdir -p 
> > /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/stage/usr/local/etc/icingaweb2
> > /bin/mkdir -p 
> > /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/stage/usr/local/share/examples/icingaweb2/apache
> > (cd 
> > /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/stage/usr/local/www/icingaweb2 
> > &&  ICINGAWEB_CONFIGDIR=/nonexistent  ./bin/icingacli setup config 
> > webserver apache --path=/icingaweb2  
> > --root=/usr/local/www/icingaweb2/public --config=/usr/local/etc/icingaweb2  
> > --file=/wrkdirs/usr/ports/net-mgmt/icingaweb2/work/stage/usr/local/share/examples/icingaweb2/apache/icingaweb2.conf)
> > 
> > Fatal error: Uncaught ErrorException: "continue" targeting switch is 
> > equivalent to "break". Did you mean to use "continue 2"? in 
> > /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/stage/usr/local/www/icingaweb2/library/Icinga/Application/Modules/Module.php:689
> > Stack trace:
> > #0 
> > /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/stage/usr/local/www/icingaweb2/library/Icinga/Application/ClassLoader.php(303):
> >  Icinga\Application\ApplicationBootstrap->Icinga\Application\{closure}(2, 
> > '"continue" targ...', '/wrkdirs/usr/po...', 689, Array)
> > #1 
> > /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/stage/usr/local/www/icingaweb2/library/Icinga/Application/ClassLoader.php(303):
> >  require()
> > #2 [internal function]: 
> > Icinga\Application\ClassLoader->loadClass('Icinga\\Applicat...')
> > #3 
> > /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/stage/usr/local/www/icingaweb2/library/Icinga/Application/Modules/Manager.php(227):
> >  spl_autoload_call('Icinga\\Applicat...')
> > #4 
> > /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/stage/usr/local/www/icingaweb2/library/Icinga/Application/Application
> >  in 
> > /wrkdirs/usr/ports/net-mgmt/icingaweb2/work/stage/usr/local/www/icingaweb2/library/Icinga/Application/Modules/Module.php
> >  on line 689
> > *** Error code 255
> > 
> > Stop.
> > make: stopped in /usr/ports/net-mgmt/icingaweb2
> 
> I’ve also found this Debian issue:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914457
> 
> Are you working on a fix? Otherwise, I might give porting the Debian change 
> as a local patch.
> 
Hi Stefan,

thanks for reporting this. I can work on this in a couple of days. If
you could work on a patch before, I won't be mad at you. :)

Lars
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Fwd: FreeBSD ports you maintain which are out of date

[Lars Engels]

On Sun, Mar 17, 2019 at 10:48:12AM +, Dima Pasechnik wrote:
> 
> I just got an email from portscout about
> www/squidclamav/ port. Indeed, it has no maintainer:
> https://www.freshports.org/www/squidclamav/
> 
> but the point of this email is a total mystery, probably just an
> error, no? I never touched this port, for sure...
> 
> I think it's OK if once upon a time an email listing all the
> un-maintained ports is sent around,
> but otherwise it's merely spam.
>

You're subscribed to po...@freebsd.org mailing list, so you also receive
portscout's mails to this address. Unmaintained ports have it as
MAINTAINER address.
Portscout only sents out a single mail when it finds a new upstream
version, so it's no spam.
Many ports unmaintained ports have received updates and some even got a
new maintainer because of portscount's mails to this mailing list.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Request for commit approval audio/virtual_oss

[Lars Engels]

On Thu, Mar 28, 2019 at 09:31:17PM +0100, Hans Petter Selasky wrote:
> Update virtual_oss to latest version, 1.2.1.
> 
> Among other features and bugfixes virtual_oss now can do simple FIR 
> filtering on the played back or recorded audio.
> 
> Approved by: lme

:-)
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Looking to port weasyprint

[Lars Engels]

On Mon, May 20, 2019 at 04:00:00PM +0200, Kurt Jaeger wrote:
> Hi!
> 
> > A simple testbuild in poudriere after some cleanup seems to work.
> > I'm testbuilding right now.
> 
> Committed as r502116, print/py-weasyprint, with the following
> description:
> 
> WeasyPrint helps web developers to create PDF documents. It turns simple
> HTML pages into gorgeous PDF.
> 
> WWW: https://weasyprint.org/
> 

Thanks, but it does not work, yet:

$ weasyprint http://weasyprint.org /tmp/weasyprint-website.pdf

Traceback (most recent call last):
  File "/usr/local/bin/weasyprint", line 6, in 
from pkg_resources import load_entry_point
  File "/usr/local/lib/python3.6/site-packages/pkg_resources/__init__.py", line 
3241, in 
@_call_aside
  File "/usr/local/lib/python3.6/site-packages/pkg_resources/__init__.py", line 
3225, in _call_aside
f(*args, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/pkg_resources/__init__.py", line 
3254, in _initialize_master_working_set
working_set = WorkingSet._build_master()
  File "/usr/local/lib/python3.6/site-packages/pkg_resources/__init__.py", line 
583, in _build_master
ws.require(__requires__)
  File "/usr/local/lib/python3.6/site-packages/pkg_resources/__init__.py", line 
900, in require
needed = self.resolve(parse_requirements(requirements))
  File "/usr/local/lib/python3.6/site-packages/pkg_resources/__init__.py", line 
786, in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'CairoSVG>=1.0.20' distribution was not 
found and is required by WeasyPrint

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Checking you the maintainer of a port?

[Lars Engels]

On Wed, Nov 27, 2019 at 09:07:55PM +, Brooks Davis wrote:
> On Wed, Nov 27, 2019 at 02:05:56PM -0700, Janky Jay, III wrote:
> > Hello,
> > 
> > On 11/27/19 2:03 PM, @lbutlr wrote:
> > > I thought that the maintainer of a port was listed somewhere in the files 
> > > at user/ports//portbase/ but evidently not. What is the easiest 
> > > way to find out, sitting in console on a server without a GUI, to find 
> > > out who the maintainer is? (On my desktop I can just google and launch a 
> > > browser, but that is not possible on most of the servers which do not 
> > > have web clients installed.
> > > 
> > > (Right now I am looking for the maintainer of roundcube, but this is a 
> > > general question.)
> > > 
> > 
> > Please see the "MAINTAINER=" line in the port's "Makefile".
> 
> A slightly more general answer is:
> 
> cd /usr/ports//; make -V MAINTAINER

There's already a target for it:

  make maintainer

in a port's directory.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

devel/llvm80 port on 12.1

[Lars Engels]

I'm trying reduce the size of the NomadBSD image and the biggest
installed package is devel/llvm80 with 848 MiB.
llvm80 is a dependency of graphics/mesa-dri which is needed for
x11-servers/xorg-server.

Looking at the llvm version of 12.1-RELEASE in base I see that it is the
same version like the installed port:

$ /usr/bin/clang --version
FreeBSD clang version 8.0.1 (tags/RELEASE_801/final 366581) (based on LLVM 
8.0.1)
Target: x86_64-unknown-freebsd12.1
Thread model: posix
InstalledDir: /usr/bin

$ /usr/local/llvm80/bin/clang --version
clang version 8.0.1 (tags/RELEASE_801/final)
Target: x86_64-portbld-freebsd12.0
Thread model: posix
InstalledDir: /usr/local/llvm80/bin

So it looks like on 12.1 the mesa-dri port can use the base llvm instead
of the one from ports and save all people running Xorg almost 1 GB of
disk space?

-- 
Lars
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: devel/llvm80 port on 12.1

[Lars Engels]

On Thu, Dec 12, 2019 at 10:50:00AM -0500, Kevin P. Neal wrote:
> On Thu, Dec 12, 2019 at 04:42:07PM +0100, Lars Engels wrote:
> > I'm trying reduce the size of the NomadBSD image and the biggest
> > installed package is devel/llvm80 with 848 MiB.
> > llvm80 is a dependency of graphics/mesa-dri which is needed for
> > x11-servers/xorg-server.
>
> As a build dependency or a run-time dependency? If build only then you can
> remove it assuming you are using packages.

mesa-dri's Makefile.common has:

USE+= compiler:c++11-lib

.if ${LLVM_DEFAULT:S,-devel,990,} >= 90
LLVM_DEFAULT=   80
.endif

.if ${ARCH} == aarch64 || ${ARCH} == amd64 || ${ARCH:Marm*} || ${ARCH} == i386 
|| ${ARCH:Mmips*} || ${ARCH:Mpowerpc*}
BUILD_DEPENDS+= llvm${LLVM_DEFAULT}>=3.9.0_4:devel/llvm${LLVM_DEFAULT}
.if ${COMPONENT} != libs
RUN_DEPENDS+=   llvm${LLVM_DEFAULT}>=3.9.0_4:devel/llvm${LLVM_DEFAULT}
.endif
CONFIGURE_ENV+= LLVM_CONFIG=${LOCALBASE}/bin/llvm-config${LLVM_DEFAULT}
LDFLAGS+=   -Wl,-rpath=${LOCALBASE}/llvm${LLVM_DEFAULT}/lib
CONFIGURE_ARGS+=--enable-llvm
.else
CONFIGURE_ARGS+=--disable-llvm
.endif

and Makefile has:


.if ${ARCH} == aarch64 || ${ARCH} == amd64 || ${ARCH:Marm*} || ${ARCH} == i386 
|| ${ARCH:Mmips*} || ${ARCH:Mpowerpc*}
GALLIUM_DRIVERS=SWRAST  # llvmpipe


>
> > Looking at the llvm version of 12.1-RELEASE in base I see that it is the
> > same version like the installed port:
>
> > So it looks like on 12.1 the mesa-dri port can use the base llvm instead
> > of the one from ports and save all people running Xorg almost 1 GB of
> > disk space?
>
> Does the base clang have all the features that the ports/packages clang
> has? They may have left out bits of clang that are not needed for the
> base system.
>
> That may be why the port is required by something graphics related.

That could be. Maybe someone from x11@ knows more.

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: devel/llvm80 port on 12.1

[Lars Engels]

On Thu, Dec 12, 2019 at 06:06:52PM +0100, Jan Beich wrote:
> Lars Engels  writes:
> 
> > So it looks like on 12.1 the mesa-dri port can use the base llvm instead
> > of the one from ports and save all people running Xorg almost 1 GB of
> > disk space?
> 
> Does the patch in bug 242607 help?

Yes, thank you. It works for me on my Thinkpad T450s with HD Graphics 5500.
I wonder if that's also true for AMD and nvidia users.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Pkg repository is broken...

[Lars Engels]

On Wed, Mar 04, 2020 at 03:16:14PM +1100, Greg 'groggy' Lehey wrote:
> On Monday,  2 March 2020 at 17:58:01 +, marco wrote:
> > On Sun, Mar 01, 2020 at 04:50:59PM -0500, you (Brennan Vincent) sent the 
> > following to [freebsd-current] :
> >> Apparently something has its ABI erroneously listed as FreeBSD:13.0:amd64
> >> instead of FreeBSD:13:amd64.
> >>
> >> ```
> >> $ sudo pkg update -f
> >> Updating FreeBSD repository catalogue...
> >> Fetching meta.conf: 100%163 B   0.2kB/s00:01
> >> Fetching packagesite.txz: 100%6 MiB   6.4MB/s00:01
> >> Processing entries:  72%
> >> pkg: wrong architecture: FreeBSD:13.0:amd64 instead of FreeBSD:13:amd64
> >> pkg: repository FreeBSD contains packages with wrong ABI: 
> >> FreeBSD:13.0:amd64
> >> Processing entries: 100%
> >> Unable to update repository FreeBSD
> >> Error updating repositories!
> >
> > Ran into this very same problem today too.
> > Just learned on #freebsd that the repos are temporarily borked and
> > people are working hard to fix it.
> 
> Any workarounds in the meantime?  This must affect a lot of people,
> including those who use 12-:
> 
>   pkg: wrong architecture: FreeBSD:12.0:amd64 instead of FreeBSD:12:amd64
>   pkg: repository FreeBSD contains packages with wrong ABI: FreeBSD:12.0:amd64

Still broken for me on 12.1.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [HEADS UP] Planned deprecation of portsnap

[Lars Engels]

On Tue, Aug 04, 2020 at 02:43:20PM -0400, Steve Wills wrote:
> 
> We are planning to deprecate use of portsnap in ports.
> 
> The reasons are as follows (in no particular order):
> 
> * Portsnap doesn't support quarterly branches, even years after 
> quarterly branches were created and changed to the default for non-HEAD 
> packages.
> 
> * Portsnap doesn't seem to save disk space compared to svn or git, if 
> you count the metadata (stored in /var/db/portsnap by default) and you 
> do an apples-to-apples comparison of svn or git without history and 
> ignoring possible ZFS compression. That is, you use "svn export" or git 
> "clone --depth 1", you see this disk usage:
> 
>  342Msvnexport
>  426Mgit
>  477Mportsnap
> 
> * Portsnap also doesn't work offline which git does. With git, you can 
> also easily add the history by running "git pull --unshallow"
> 
> * This migration away from portsnap fits well with the planned migration 
> to git.
> 
> * Also based on the patches we've seen in Bugzilla for some time, usage 
> of portsnap causes folks to too easily accidentally submit patches to 
> Bugzilla which don't apply easily.
> 
> * Since portsnap doesn't support quarterly branches, it often causes 
> users to build on the wrong branch or end up with mismatched packages. 
> That is, they install packages from quarterly via pkg, then want to 
> customize so run portsnap and build from head, which can cause problems, 
> as we often see. Even when this doesn't happen, it adds to 
> troubleshooting to verify that it didn't.
> 
> We are aware people have gotten used to portsnap, but believe:
> 
> * People should be able to easily use svnlite in base or git from pkgs. 
> (Very few people seem to actually use WITHOUT_SVNLITE).
> 
> * There is also the possibility of falling back to fetching a tar or zip 
> from https://cgit-beta.freebsd.org/ports/ although this does make 
> updating harder.
> 
> How it will be done, in order:
> 
> * Update poudriere to use svn by default. This is already done:
> 
>https://github.com/freebsd/poudriere/pull/764
>  
> https://github.com/freebsd/poudriere/commit/bd68f30654e2a8e965fbdc09aad238c8bf5cdc10
> 
> * Update docs not to mention portsnap. This is already in progress:
> 
>https://reviews.freebsd.org/D25800
>https://reviews.freebsd.org/D25801
>https://reviews.freebsd.org/D25803
>https://reviews.freebsd.org/D25805
>https://reviews.freebsd.org/D25808
>https://svnweb.freebsd.org/changeset/base/363798
> 
>Many thanks to the folks who have worked and are working on this!
> 
> * Make WITHOUT_PORTSNAP default in base. Currently not certain when this 
> will happen. May not happen before 13.0, but hopefully it will.
> 
> * Eventually, portsnap servers will see low enough usage they can be 
> disabled.
> 
> We welcome any constructive feedback. All input would be heard, and if 
> the plans need to be amended, we will come back to you with the amended 
> plan in a couple of weeks. This process will take some time and 
> hopefully won't be too disruptive to anyone's usual workflow.
> 

I'm probably fine with this and I think that all of the (now) supported
methods have pros and cons.
To leverage the UX flaws of git and svn(lite) compared to portsnap
having a wrapper script around the two tools would be very appreciated.

Something like

# portsnap-ng --mode git --branch 2020Q2 --destination /ports/2020Q2 fetch 
extract
  The package devel/git does not seem to be installed, do you want to install 
it? (Y/n) _

With sane defaults, so you can just run portsnap fetch extract like
you're used to and this
downloads the latest ports tree to /usr/ports using base svnlite(1).

While we're here: Can we please have a separate user that is used to
checkout the tree? 

Lars


P.S.: Please DO NOT name the wrapper portsnap-ng. :-)
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: icinga-1.8.1

[Lars Engels]

On Thu, Nov 15, 2012 at 03:09:36PM -0500, Samantha Smith wrote:
> Hello,
> I'm contacting you today wondering if the Icinga port for FreeBSD is still
> being maintained, as the link
> http://www.freebsd.org/cgi/cvsweb.cgi/ports/net-mgmt/icinga/  no longer
> exists and
> http://cvsweb.freebsd.org/ports/net-mgmt/icinga found after searching at
> http://www.freebsd.org/cgi/ports.cgi?query=icinga&stype=all
> seems to no longer exist as well.
> At the worst, I'm reporting dead links for now-unmaintained packages, and
> in such a case I will build from the source supplied by the original Icinga
> project.
> At the best, I'm hoping to hear the port is still being maintained.

Like the other ones already said, the port is still being maintained,
and I do my very best to keep it in a good shape. :)

Lars


pgp24AxYhb9eL.pgp
Description: PGP signature

Re: opera 12.11

[Lars Engels]

On Tue, Nov 27, 2012 at 05:55:45PM -0600, ajtiM wrote:
> On Tuesday 27 November 2012 17:24:31 Kevin Oberman wrote:
> > On Tue, Nov 27, 2012 at 1:40 PM, ajtiM  wrote:
> > > On Tuesday 27 November 2012 08:08:45 Peter Ulrich Kruppa wrote:
> > >> On 27.11.2012 12:34, ajtiM wrote:
> > >> > Hi!
> > >> > 
> > >> > Update to Opera 12.11 and Opera-Linuxplugins 12.11 from 12.10 on my
> > >> > FreeBSD 9.1 RC-3 doen't works anymore:
> > >> > 
> > >> > opera
> > >> > libpng error: incorrect data check
> > >> > libpng error: incorrect data check
> > >> > libpng error: incorrect data check
> > >> > Segmentation fault (core dumped)
> > >> 
> > >> It is quite a while since, but did you update your graphics/png
> > >> properly? Please check /usr/ports/UPDATING 20120531 .
> > >> 
> > >> Greetings
> > >> 
> > >> Peter
> > >> 
> > >> > Thanks in advance.
> > >> > 
> > >> > P.S.
> > >> > 
> > >> > I used Clang to build Opera.
> > >> > 
> > >> > Mitja
> > >> > 
> > >> > http://www.redbubble.com/people/lumiwa
> > >> > ___
> > >> > 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"
> > > 
> > > As I remember I did portmaster -r png- and it build one day
> > > 
> > > Opera 12.10 and before didn't have problems...
> > 
> > Try "pkg_libchk -o". If you don't have it, install
> > sysutils/bsdadminscripts. It can save a LOT of time over portmaster -r
> > as many ports that will be re-installed with portmaster are dependent
> > on other ports that use png, but don't use it directly, so don't need
> > to be re-built. In many cases only about 10% of the ports that
> > "depend" on some library actually link to the sharable, though png is
> > linked to far more things than most.
> > 
> > An occasional run will also catch oversights, like missing an UPDATING
> > entry or having a shareable version updated, but not entered into
> > UPDATING.  I think it should be a part of the weekly periodic run. (I
> > also think it should be in the base system.)
> > 
> > I am not sure if pkg_libchk works with pkgng. Dominic?
> 
> I am running pkg_libck -o and everything is corrup because it calls pkg_info 
> (I use pkgng).

In pkg_libchk you have to change pkg_info -> pkg info and in one place
remove a parameter to pkg_* that pkg doesn't understand. -E IIRC. 


pgpUQkRWRxyvc.pgp
Description: PGP signature

Re: Discussion concerning: New dialog for ports

[Lars Engels]

On Thu, Nov 29, 2012 at 05:12:55PM +0400, Ilya A. Arkhipov wrote:
> Hi Folks,
> 
> Few week ago I started work on new dialog for ports, main idea it's adding 
> functionality, I guess you know ;)
> I took checklist.c from libdialog and modified it for us. Regarding license, 
> I discussed with Thomas E. Dickey(author dialog) he said I can't change LGPL 
> to BSD but it should not be a problem.
> What we have now:
> - check + radio lists in on box (and yes we can put off radiobox)
> - separate line with text
> - dynamic width/height size
> - all features from checklist.c :)
> -- mouse support
> -- hotkey for find a lines
> My plan:
> - add Help button/F1/alt-h/esc-1 (actually don't know how will be better)
> - button for license
> - fixing bugs >_<
> - start work on parsing receiving data, after that should be ready for 
> testing.
> 
> Regarding parsing data I want discuss here. Wanna correct understand what 
> will be better, now I have few variants:
> 1. Get all data from env. variables
> 2. Use the same with old dialog style, I mean receive from STDIN
> 3. From file? <- guess bad idea
> Your ideas?
> 
> And certainly screeshots:
> Big description(just for test);
>   In X -- http://imm.io/NkVR
>   In Terminal -- 
> https://www.dropbox.com/s/bzt8zszpk40jrso/2012-11-29%2014.59.53.jpg
> With license button:
>   in X -- http://imm.io/Nl9K
> 
> You can find my repo there: https://bitbucket.org/m1cro/d4p/. I'll be happy 
> for all response ;)
> 


That look very good! :)


pgpHEKTfpARw9.pgp
Description: PGP signature

Adopt an orphaned port project

[Lars Engels]

Since the ports tree is now open again, let's start the "Adopt an orphaned port"
project.


=== What is it? ===

According to http://freshports.org/ we currently have 23,940 ports in our tree,
that's really great!
But: There are 4,751 unmaintained ports (approx. 20%), that need _your_ love.


=== What can I do? ===

Adopt one or more ports!

You think it's a lot of work? 

That's not necessarily the case, the ports are already there and just need
someone to track the latest upstream versions and someone who keeps the port in
a good shape.


=== How do I know which ports are unmaintained? ===

Thats pretty easy: If you want a list of all unmaintained ports, run

# nawk -F"|" '$6 == "po...@freebsd.org" {print $2}' /usr/ports/INDEX-`uname -r 
|\
  cut -d'.' -f1`

If you want to see which of your installed ports are unmaintained run

a) for pkgng

# pkg query -e "%m == 'po...@freebsd.org'" %o

b) for pkg_*

--- 8<  8< -- 8< - 8<  8< -
#!/bin/sh

INDEX="/usr/ports/INDEX-$(uname -r | cut -d'.' -f1)"
MAINTAINER="po...@freebsd.org"

grep -h ORIGIN /var/db/pkg/*/+CONTENTS | cut -d: -f2 |
  nawk -v INDEX="$INDEX"  -v MAINTAINER="$MAINTAINER" \
'{ installed_ports[$0] = 1 }
END {
FS="|"
while (getline < INDEX) {
if ($6 == MAINTAINER) {
sub(/\/usr\/ports\//, "", $2)
unmaintained_ports[$2] = 1 
};
}
for (port in installed_ports) {
if (unmaintained_ports[port]) {
print port
}
}
}' | sort
--- 8<  8< -- 8< - 8<  8< -


=== What can I do then? ===

Pick a port, take a look at the port's Makefile and pkg-descr, see if a new
version is avaiable upstream, check if the WWW line in pkg-descr still points
to a valid site.
Check for broken distfile mirrors, take a look at

http://people.freebsd.org/~ehaupt/distilator/po...@freebsd.org-bad.html

Find other mirrors, or mirror the distfiles yourself, remove the dead mirrors
from the port's Makefile.

Try to update the port to the new version, add yourself as MAINTAINER in the
Makefile.
If the updated port works, create a patchfile and send a problem
report (PR) with send-pr(1) or via the web interface

http://www.freebsd.org/send-pr.html

All you need then is some patience until some committer grabs the PR and
eventually commits it or ask you to re-work the patch, if there are some issues
left.


=== I'd really like to do that, but how do I actually do it? ===

There's very good documentation for porters: The porter's handbook:

http://www.freebsd.org/doc/en/books/porters-handbook/

Don't worry. It's called a book, but it's not a very thick book. Even so it
explains porting very good.
While it's recommended to read the whole book you can also pick the chapters
first that you need to update the port.
If you still have problems or questions then, there are many helpful people at
the po...@freebsd.org mailing list.


=== What benefits do I have? ===

Actually there a several benefits:
- You give something back to the community. That's the idea of open source.
- You earn experience with Makefiles, diff(1), patch(1) and other useful tools.
- You and everyone benefits from updated ports
- Your names get added to the list of FreeBSD Contributors

  http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributors/index.html

- If you create enough PRs and maintain a bunch of ports, it's quite possible 
that
  you get punished with a ports commit bit! \o/




pgpQPemiWNUwQ.pgp
Description: PGP signature

Re: Dropbox on FreeBSD

[Lars Engels]

On Wed, Dec 19, 2012 at 09:23:47AM -0500, Jerry wrote:
> On Wed, 19 Dec 2012 14:32:57 +0100
> Frank Staals articulated:
> 
> > Jerry  writes:
> > 
> > > I was asked about the feasibility of setting up Dropbox
> > >  on a FreeBSD machine,
> > > specifically under KDE if possible. I found three references to
> > > Dropbox in the ports tree; however, I am not sure that they are
> > > exactly what I am looking for. Does anyone have any experience with
> > > this software or specific information on it?
> > 
> > As far as I know it is currently impossible to run dropbox on FreeBSD,
> > as it requires inotify, as found in the Linux kernel, to detect when
> > files have changed. 
> 
> Thanks, I told the individual that I didn't think it would work. I saw
> something on a forum regarding it. I don't remember exactly what it
> referred to though. It is not going to happen in v.9.x of FreeBSD;
> however, perhaps before bumping the version to v.10, someone
> might get this resolved. However, sometimes I wonder if certain
> individuals are more interested in bumping version numbers as opposed
> to putting out fully functional software.

AFAIK the Windows versions works with WINE.


pgp7w88FO5TED.pgp
Description: PGP signature

Re: update for DESKTOP_ENTRIES framework

[Lars Engels]

On Wed, Jan 02, 2013 at 01:45:52PM +, Max Brazhnikov wrote:
> Hi folks,
> 
> I propose an update for DESKTOP_ENTRIES:
> http://people.freebsd.org/~makc/patches/desktop_entry_20130102.diff
> 
> Changes:
> - update list of categories to the version 1.1 of Desktop Menu Specification
> - require Icon field to follow Desktop Entry Specification (the field must be
>   absolute path or icon name if icon theme is used)
> - require main category to be set (listed in DESKTOP_CATEGORIES_MAIN)
> - remove deprecated Encoding key
> - allow StartupNotify field to be empty string
> - be less strict when generating filename for desktop entry (to improve
>   readability when full path to executable is used)
> - use port ${COMMENT} if comment field is not set
> - add GenericName key (comment field will be used)
> 
> About 20 ports will throw warnings about icon field, several ports don't set
> main category, about 60 use non-standard 'Application' for categories.
> I'm willing to fix them all.
> 
> Review and suggestion are welcome!
> 
> Happy New Year!
> Max

Great idea, thanks!

Please also update the porter's handbook when you commit the changes.


pgpdzq4d5BtgO.pgp
Description: PGP signature

Re: Writing port makefile

[Lars Engels]

On Wed, Feb 13, 2013 at 03:34:59PM +, Gary J. Hayers wrote:
> On 13/02/2013 15:30, Chris Rees wrote:
> > On 13 Feb 2013 15:20, "Gary J. Hayers"  wrote:
> > First define NO_BUILD=yes, and then make a do-install target.
> >
> > What type of files, and to where?
> >
> > Chris
> 
> Thanks Chris, as it happens I found the NO_BUILD=yes target just after I 
> mailed the list. there will be 3 files installed in 
> /usr/share/doc/%{PORTNAME} and 1 file in /usr/local/bin. So I just have 
> to learn a little of the do-install target now.

Don't forget to read the Porter's Handbook first:

http://www.freebsd.org/doc/en/books/porters-handbook/book.html


pgpE_1mMb7Biz.pgp
Description: PGP signature

Re: Writing port makefile

[Lars Engels]

On Wed, Feb 13, 2013 at 06:25:18PM +, Gary J. Hayers wrote:
> On 13/02/2013 17:49, Gary J. Hayers wrote:
> > On 13/02/2013 15:40, Gary J. Hayers wrote:
> >> Thanks Lars, I am going through it slowly, it's not like the first port
> >> I ported which was fairly easy in comparison.
> >
> > Ok sor got that going now but after I run make I get:
> > "Makefile", line 19: Need an operator
> > make: fatal errors encountered -- cannot continue
> >
> > Anyone got any thoughts? Below is my Makefile or partial anyway
> >
> > LICENSE=GPLv2
> > LICENSE_FILE=   ${WRKSRC}/gpl.txt
> >
> > RUN_DEPENDS=p5-NNTPClient:${PORTSDIR}/news/p5-NNTPClient
> >
> > NO_BUILD=   yes
> >
> > do-install:
> >  ${INSTALL_SCRIPT} ${WRKSRC}/script ${PREFIX}/bin
> >  ${MKDIR} ${PREFIX}/doc/${PORTNAME}
> >  ${INSTALL_DATA} ${WRKSRC}/README.txt ${PREFIX}/doc/${PORTNAME}
> >  ${INSTALL_DATA} ${WRKSRC}/Changelog ${PREFIX}/doc/${PORTNAME}
> >  ${INSTALL_DATA} ${WRKSRC}/gpl.txt ${PREFIX}/doc/${PORTNAME}
> >
> > .include 
> 
> Scratch that, got it working. Many thanks all

I would suggest that you add a trailing / to the ${INSTALL_} macros if
you want to install into a directory, so you get an error if the
directory does not exist, for what reason ever.


pgp5UdoBwzK1d.pgp
Description: PGP signature

Re: Proposal: do not show up the dialog(1) by default?

[Lars Engels]

On Thu, May 23, 2013 at 07:45:42AM +0200, Baptiste Daroussin wrote:
> hi,
> 
> A lot of people seems to be complaining about the configuration dialog popping
> up all the time.
> 
> What if we change the default behaviour to not pop up the dialog each time 
> there
> is a changed option but only when the user explicitly type make config?
> 
> Just a proposal, please give your opinion.
> 
> Of course make config-recursive behaviour won't change.
> 
> regards,
> Bapt

I am strongly against it. Firstly, it's against POLA, secondly, while it
hides complexity of the ports system it also hides its biggest
advantage.
You'll never know which knobs the ports you want to build offer and new
users will never find out how to build an Apache web server with PHP
support.

My proposal get rid of the nagging NLS and DOCS window, ask the user
initially if they want NLS and DOCS and enable/disable it globally.
Second, encourage the use of portmaster to install new ports, which
recursively displays the OPTIONS dialog and does this much faster than
make config-recursive.
That way you can set/unset all OPTIONS, go to bed and don't find an
unanswered dialog in the next morning.

Lars



pgpd438vBAfsX.pgp
Description: PGP signature

Re: The vim port needs a refresh

[Lars Engels]

On Tue, May 28, 2013 at 07:51:37PM +0200, Michael Gmelin wrote:
> On Tue, 28 May 2013 15:16:00 +0100
> RW  wrote:
> 
> > On Tue, 28 May 2013 15:14:52 +0200
> > John Marino wrote:
> > 
> > > All
> > > patches only take 74 seconds to download[2] so there is no sympathy
> > > for your obviously single data point anecdote, 
> > 
> > Well at the point you provided one data-point there was only one data
> > point. And it was like pulling teeth to get you to eliminate the
> > alternative explanations. Was it really too much to ask that you
> > provided some actual evidence. 
> > 
> > > you're clearly doing
> > > something wrong.  You need to stop complaining and start think about
> > > folks with slow connections[3] who also rebuild Vim frequently. 
> > 
> > Don't make things up. I never said anything about frequent rebuilds,
> > the patches all get redownloaded on the next rebuild. 
> 
> The real issue is not the number of patches, but the fact that every
> single patch is downloaded by invoking the fetch(1) command, creating
> lots of overhead not limited to the fetch command itself. The ports
> system wasn't designed for such an amount of distfiles in a single
> port I guess.
> 
> I just timed fetching the patches through ports vs. fetching over
> HTTP/1.1 using ftp/curl vs calling fetch directly. The VIM tarball was
> already downloaded, so this is really just the patches (plus
> downloading 6mb is barely noticeable on a fast line). It's a slow
> machine on a fast line.
> 
> Fetch:
> [user@server /usr/ports/editors/vim]$ time sudo make fetch
> 
> real4m57.327s
> user0m17.010s
> sys 0m39.588s
> 
> Curl:
> [user@server /tmp]$ longcurlcommandline 
> 
> real0m15.291s
> user0m0.026s
> sys 0m0.272s
> 
> Fetch on the command line (after initial make fetch, so this is only
> measuring transmission of the files):
> cd /usr/ports/editors/distfiles
> time for name in 7.3.*; do
>   fetch http://artfiles.org/vim.org/patches/7.3/$name
> done
> 
> real1m25.329s
> user0m0.660s
> sys 0m3.174s
> 
> So just the fact we're invoking fetch for every file costs us about one
> minute - I assume the time lost is much bigger on a slow line with
> long latency. The remaining 3.5 minutes are spent somewhere in the
> ports infrastructure and clearly depend on the performance of the
> machine used. For comparison I timed "make fetch" on a reasonably fast
> server (good IO, fast datacenter connection), make fetch still took
> about 120 seconds(!).
> 
> So the bottomline is:
> - Using HTTP/1.1 and keepalive could safe a lot of time
> - The ports infrastructure creates a lot of overhead per patch file
> 
> Maybe there's something we can do to improve the situation.
> 
> Cheers,
> Michael
> 
> PS: I don't use vim myself and have no stake in this discussion
> whatsoever.

Someone in this thread proposed to change the port to use phttpget, so I
gave it a try using a German mirror nearby with 6 Mbit/s downlink:

$ time /usr/libexec/phttpget ftp.vim.ossmirror.de $(eval echo 
/pub/vim/patches/7.3/{$(make -C /usr/ports/editors/vim -VPATCHFILES | sed 's/\ 
/,/g')})
http://ftp.vim.ossmirror.de//pub/vim/patches/7.3/7.3.001: 200 OK
http://ftp.vim.ossmirror.de//pub/vim/patches/7.3/7.3.002: 200 OK
http://ftp.vim.ossmirror.de//pub/vim/patches/7.3/7.3.003: 200 OK
http://ftp.vim.ossmirror.de//pub/vim/patches/7.3/7.3.004: 200 OK
http://ftp.vim.ossmirror.de//pub/vim/patches/7.3/7.3.005: 200 OK
[...]
http://ftp.vim.ossmirror.de//pub/vim/patches/7.3/7.3.974: 200 OK
http://ftp.vim.ossmirror.de//pub/vim/patches/7.3/7.3.984: 200 OK
http://ftp.vim.ossmirror.de//pub/vim/patches/7.3/7.3.985: 200 OK
http://ftp.vim.ossmirror.de//pub/vim/patches/7.3/7.3.1000: 200 OK

real0m12.509s
user0m0.154s
sys 0m0.089s


That's really nice! 

Compare this to the current version using fetch(1):

 time make PATCH_SITES=http://ftp.vim.ossmirror.de/pub/vim/patches/7.3/ fetch
===>  Found saved configuration for vim-7.3.669_1
===>   vim-7.3.1014 depends on file: /usr/local/sbin/pkg - found
=> 7.3.002 doesn't seem to exist in /usr/ports/distfiles/vim.
=> Attempting to fetch http://ftp.vim.ossmirror.de/pub/vim/patches/7.3/7.3.002
7.3.002   100% of 1610  B   16 MBps 00m00s
=> 7.3.003 doesn't seem to exist in /usr/ports/distfiles/vim.
=> Attempting to fetch http://ftp.vim.ossmirror.de/pub/vim/patches/7.3/7.3.003
7.3.003   100% of 1299  B 1281 kBps 00m00s
=> 7.3.004 doesn't seem to exist in /usr/ports/distfiles/vim.
[...]
=> 7.3.984 doesn't seem to exist in /usr/ports/distfiles/vim.
=> Attempting to fetch http://ftp.vim.ossmirror.de/pub/vim/patches/7.3/7.3.984
7.3.984   100% of 1706  B 2852 kBps 00m00s
=> 7.3.985 doesn't seem to exist in /usr/ports/distfiles/vim.
=> Attempting to fetch http://ftp.vim.ossmirror.de/pub/vim/patches/7.3/7.3.985
7.3.985   100% of 1691  B   14 MBps 00m00s
=> 7.3.100

Re: Searching the port tree with portmaster?

[Lars Engels]

On Fri, Aug 16, 2013 at 08:35:31AM +0300, Sergey V. Dyatko wrote:
> On Thu, 15 Aug 2013 12:12:41 -0400
> Jim Trigg  wrote:
> 
> > On Thu, Aug 15, 2013 at 09:45:30AM -0600, LuKreme wrote:
> > > On 15 Aug 2013, at 00:56 , Sergey V. Dyatko
> > >  wrote:
> > > 
> > > > man ports
> > > 
> > > > /search[enter]
> > > 
> > > cd /usr/ports && make search name=pear- 
> > > cd /usr/ports && make search name=pear- xname='ht(tp|ml)'
> > > 
> > > Well, OK. That seems a lot more effort, and loses your current
> > > directory, but that does work. It's fugly though.
> > 
> > OK, so "alias search='make -C /usr/ports search'".  Then you can, as
> > needed, "search name=whatever" (or whatever criteria you want to use).
> > 
> > Jim
> 
> 2 aliases from my .cshrc:
> 
> alias search_name"make -C /usr/ports/
> search name='\!*' display=name,path,info" 
> 
> alias search_key"make -C /usr/ports/ search key='\!*'
> display=name,path,info"

There's the "quicksearch" target which does exactly display name, path
and info.

> 
> search_[name|key] smthng
> 



pgpSKNJ4fJFBJ.pgp
Description: PGP signature

Re: search for port adopters

[Lars Engels]

Am 01.10.2013 05:06, schrieb Vlad V. Teterya:

Hello!

I am no longer using FreeBSD in production and I'm interested to find
new maintainers for my ports:

databases/mysqltuner
www/oscommerce
x11/ipager
x11/tilda

If someone wants to take over this ports, splease submit PR with
maintainer update.
Thanks.


I use ipager, so I'll take that one.
___
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: search for port adopters

[Lars Engels]

Am 02.10.2013 09:07, schrieb Jason Helfman:

On Tue, Oct 1, 2013 at 11:55 PM, Lars Engels 
wrote:


Am 01.10.2013 05:06, schrieb Vlad V. Teterya:


Hello!

I am no longer using FreeBSD in production and I'm interested to
find
new maintainers for my ports:

databases/mysqltuner
www/oscommerce
x11/ipager
x11/tilda

If someone wants to take over this ports, splease submit PR with
maintainer update.
Thanks.


I use ipager, so I'll take that one.


Done. This needs STAGEDIR support, as previously mentioned.

Thanks!



Yup, I'll try to get my ports to support staging during the next days.
___
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: Chromium and HEAD

[Lars Engels]

On Wed, Oct 02, 2013 at 10:10:24PM -0400, Sam Fourman Jr. wrote:
> using a recent FreeBSD amd64
> FreeBSD NewBSD 10.0-ALPHA4 FreeBSD 10.0-ALPHA4 #0 r255942: Sun Sep 29
> 20:05:41 UTC 2013
> 
> 
> I am running chromium built with default options(clang33 from ports)
> when you use the address bar to search, chromium will coredump if the first
> letter you type is the letter "a"
> 
> is anyone else seeing this?
> 

Same for me using the version from pkg-test.


pgpLcCUGdOoxC.pgp
Description: PGP signature

Re: poudriere distfiles - explain the process

[Lars Engels]

Am 10.10.2013 13:56, schrieb Bryan Drewery:

On 10/10/2013 5:00 AM, Anton Shterenlikht wrote:

I've run poudriere distclean -n.
It took about an hour.
All the time /usr/ports/distfiles was empty,
which was confirmed at the end:

*skip*

OME}})
make: Fatal errors encountered -- cannot continue
clang: not found
make: "/pdr/ports/lang/v8/Makefile" line 24: warning: Couldn't read 
shell's output for "clang --version | /usr/bin/head -1 | /usr/bin/sed 
-e 's/.*clang version \([0-9]\)\.\([0-9]\).*/\1\2/'"
make: "/pdr/ports/mail/p5-Sendmail-Milter/Makefile" line 22: warning: 
Couldn't read shell's output for "/usr/local/bin/perl5.16.3 
-V:usethreads | /usr/bin/awk '/define/ { print "define"; exit }'"


>> Gathering list of actual distfiles
>> No stale distfiles to cleanup
#

So what was it doing all this time?
I think I probably misunderstand
the purpose of "poudriere distclean".
It's not just checking all exising
files under /usr/ports/distfiles
to see which are outdated, is it?
It's traversing the whole of the
ports tree, right? Why?


It is looking at every port's Makefile you specify and then comparing 
to

the distfiles you have. Perhaps it can be optimized more.



Maybe that can be written to a sqlite database?
pkgng already uses them, so poudriere could do the same.
Add the distfiles on the first run of "distclean" and then update the 
database
every time "portsnap update" is run. Maybe even better if the database 
was part

of the ports tree, just like the INDEX files.
___
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: Finding abandoned ports

[Lars Engels]

Am 30.10.2013 15:02, schrieb Alex Laurie:

Hello all,

Only really just getting into FreeBSD but I am inspired to help out. 
I'm

not a developer or anything. However I do like to install and update
things. I though one area I may be able to help out is in the ports 
side of
things. I have been through the Porters handbook and thought I would 
try
updating some out of date ports to cut my teeth so to speak. Looking 
around

I don't seem to see anywhere with abandoned ports that need some love.

Any help or pointers?



You can start by finding out which installed ports are unmaintained, 
give

them some love and maybe become a maintainer. See

http://lists.freebsd.org/pipermail/freebsd-ports/2012-December/079880.html

for details.


Lars
___
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: Official FreeBSD Binary Packages now available for pkgng

[Lars Engels]

On Thu, Oct 31, 2013 at 05:22:44PM -0500, Bryan Drewery wrote:
> On 10/31/2013 4:54 PM, Freddie Cash wrote:
> > On Thu, Oct 31, 2013 at 2:39 PM, Mehmet Erol Sanliturk <
> > m.e.sanlit...@gmail.com> wrote:
> > 
> >> On Thu, Oct 31, 2013 at 4:58 PM, Bryan Drewery 
> >> wrote:
> >>
> >> At present , the packages information and themselves are available from ,
> >> such as :
> >>
> >> ftp://ftp1.freebsd.org/pub/FreeBSD/ports/amd64/
> >>
> >> It seems that new pkg compatible packages will not be exposed to the
> >> Internet such as
> >>
> >>
> >> http://avalon.dragonflybsd.org/dports/
> >> http://pkg.wolfpond.org/
> >> http://mirror.exonetric.net/pub/pkgng/
> >>
> >>
> >> This will be a very significant inconvenience for the possible users
> >> because without an installed FreeBSD , they will not be able to see what
> >> are the available packages there .
> >>
> > 
> > ???From the original message:
> > Mirrors you may use instead of the global
> > pkg.FreeBSD.org
> > :
> > 
> > pkg.eu.FreeBSD.org 
> > pkg.us-east.FreeBSD.org 
> > pkg.us-west.FreeBSD.org 
> > 
> > 
> > pkg.freebsd.org is, basically, an alias for the above (and any other
> > mirrors that come online) and the pkg(1) tool will pick a "local" mirror
> > based on the DNS response for pkg.freebsd.org.
> > 
> > However, you are free to manually enter any of the above mirrors into your
> > pkg.conf.
> > 
> > And, you are free to browse any of the above mirrors via HTTP in any web
> > browser.
> > 
> > It's not nearly as convenient as just browsing pkg.freebsd.org, but it's
> > still possible to do so.
> 
> These are still SRV hosts as well. The real hosts can be found with
> 
> dig SRV _http._tcp.HOST HOST being the host from above lists.
> 

Please add this to pkg.conf(5) as this it not intuitive and the syntax
is a bit cumbersome.


pgp1Mr54VuCiZ.pgp
Description: PGP signature

Re: Official FreeBSD Binary Packages now available for pkgng

[Lars Engels]

On Sun, Nov 03, 2013 at 12:36:54AM +0200, Kimmo Paasiala wrote:
> On Sun, Nov 3, 2013 at 12:34 AM, Lars Engels  wrote:
> > On Thu, Oct 31, 2013 at 05:22:44PM -0500, Bryan Drewery wrote:
> >> On 10/31/2013 4:54 PM, Freddie Cash wrote:
> >> > On Thu, Oct 31, 2013 at 2:39 PM, Mehmet Erol Sanliturk <
> >> > m.e.sanlit...@gmail.com> wrote:
> >> >
> >> >> On Thu, Oct 31, 2013 at 4:58 PM, Bryan Drewery 
> >> >> wrote:
> >> >>
> >> >> At present , the packages information and themselves are available from 
> >> >> ,
> >> >> such as :
> >> >>
> >> >> ftp://ftp1.freebsd.org/pub/FreeBSD/ports/amd64/
> >> >>
> >> >> It seems that new pkg compatible packages will not be exposed to the
> >> >> Internet such as
> >> >>
> >> >>
> >> >> http://avalon.dragonflybsd.org/dports/
> >> >> http://pkg.wolfpond.org/
> >> >> http://mirror.exonetric.net/pub/pkgng/
> >> >>
> >> >>
> >> >> This will be a very significant inconvenience for the possible users
> >> >> because without an installed FreeBSD , they will not be able to see what
> >> >> are the available packages there .
> >> >>
> >> >
> >> > ???From the original message:
> >> > Mirrors you may use instead of the global
> >> > pkg.FreeBSD.org<http://pkg.freebsd.org/>
> >> > :
> >> >
> >> > pkg.eu.FreeBSD.org <http://pkg.eu.freebsd.org/>
> >> > pkg.us-east.FreeBSD.org <http://pkg.us-east.freebsd.org/>
> >> > pkg.us-west.FreeBSD.org <http://pkg.us-west.freebsd.org/>
> >> >
> >> >
> >> > pkg.freebsd.org is, basically, an alias for the above (and any other
> >> > mirrors that come online) and the pkg(1) tool will pick a "local" mirror
> >> > based on the DNS response for pkg.freebsd.org.
> >> >
> >> > However, you are free to manually enter any of the above mirrors into 
> >> > your
> >> > pkg.conf.
> >> >
> >> > And, you are free to browse any of the above mirrors via HTTP in any web
> >> > browser.
> >> >
> >> > It's not nearly as convenient as just browsing pkg.freebsd.org, but it's
> >> > still possible to do so.
> >>
> >> These are still SRV hosts as well. The real hosts can be found with
> >>
> >> dig SRV _http._tcp.HOST HOST being the host from above lists.
> >>
> >
> > Please add this to pkg.conf(5) as this it not intuitive and the syntax
> > is a bit cumbersome.
> 
> 
> You will never have to know that syntax unless you're one of the few
> that are behind a very restrictive firewall/proxy. The pkg client does
> all this SRV record magic internally to find out a suitable mirror.
> 

Right, but I actually happen to fall into that group at work. ;-)


pgpkmsSrY0uIi.pgp
Description: PGP signature

Re: Output change of 'pkg info' after 1.2.

[Lars Engels]

Am 2013-12-05 17:54, schrieb Yasuhiro KIMURA:

From: Baptiste Daroussin 
Subject: Re: Output change of 'pkg info' after 1.2.
Date: Thu, 5 Dec 2013 17:24:09 +0100


On Thu, Dec 05, 2013 at 04:36:00PM +0100, Michael Gmelin wrote:

On Fri, 06 Dec 2013 00:13:38 +0900 (JST)
Yasuhiro KIMURA  wrote:

> I noticed that output of 'pkg info' changed after version 1.2.
>
> If I remember correctly, 1.1.x behaved as following:
>
> - 'pkg info -q pkg-name' outputs package name with version.
> - 'pkg info pkg-name' outputs package name with version, and comment.
> - 'pkg info -f pkg-name' outputs full information.
>
> But 1.2.1 works as following:
>
> - 'pkg info -q pkg-name' outputs nothing.
> - Both 'pkg info pkg-name' and 'pkg info -f pkg-name' outputs full
>   information.

Just tested, pkg 1.1.4 vs. 1.2.1

pkg info -q pkg-name is identical on both, but "-f" vs no parameter
definitely changed and this seems like a bug to me.



It is not a bug, but intended as requested by a lot of users. To mimic 
the

pkg_info behaviour.

pkg info -q shows nothing on purpose as well as pkg info -q is used by 
the
scripts like portmaster or by the ports tree and only the return value 
is

checked
0 means something was found 1 means nothing was found.


Thank you for explanation.

Then I have one question. Is there any way to get same output as
'pkg info pkg-name' of 1.1.x? I tried some combination of options but
could not find proper one.



1.1.4 doesn't behave like you describe, but here's a universal way:

root@fbsd01:~ # pkg info pkg
pkg-1.1.4_8

root@fbsd01:~ # pkg info icinga
icinga-1.9.3_2

root@fbsd01:~ # pkg query '%n-%v' icinga
icinga-1.9.3_2

root@fbsd01:~ # pkg query '%n-%v %c' icinga
icinga-1.9.3_2 Enterprise grade open source monitoring system based on 
Nagios


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

pkg.freebsd.org behind proxy doesn't work

[Lars Engels]

Hi all,

how can I use the official pkg.freebsd.org mirror behind a corporate 
proxy server?


With 10.0-RC1, pkg-1.2.3 and the stock /etc/pkg/FreeBSD.conf I get:

# pkg update
Updating repository catalogue
pkg: http://pkg.FreeBSD.org/freebsd:10:x86:64/latest/digests.txz: 
Service Unavailable

pkg: Unable to find catalogs


So apparently the proxy doesn't do SRV lookups. I don't administer the 
proxy, so changing

that is not an option.
What can I do to use our official repository?

Lars

___
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: If ports@ list continues to be used as substitute for GNATS, I'm unsubscribing

[Lars Engels]

Am 2013-12-17 23:33, schrieb John Marino:

Over the months I've seen several ports users copy a failure log and
mail it to ports@, usually without even saying "hello".  I've tried to
discourage that behavior but other members of this mail list encourage
this method of bypassing writing PRs.  One user even proudly boasted
that sending email to ports@ is faster than writing a PR so of course 
he

was going to do that instead.



That only shows how badly GNATS sucks and that it's much more 
uncomfortable to

use than writing a mail.
I totally agree that error need to be tracked in an error tracker where 
reports
don't get lost, you have a proper history etc. pp. but GNATS is just 
ancient and

should have died in a fire a long time ago.
___
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: Share your pkg aliases

[Lars Engels]

On Thu, Apr 02, 2015 at 10:19:10PM +0200, Baptiste Daroussin wrote:
> Hi,
> 
> For pkg 1.5.0 we do plan to provide a default pkg.conf full of useful aliases,
> of course this is subjective, if you think you have added some useful aliases
> into your pkg.conf please share those so we can add them directly into the 
> next
> release.

myports: rquery -e '%m = l...@freebsd.org' %o,  # Show ports maintained by me
unmaintained: query -e '%m = po...@freebsd.org' %o, # Show unmaintained ports
csearch: search -U -c, # Search a port's short description



pgp6pV8wA4MSc.pgp
Description: PGP signature

Re: FreeBSD Port: pnp-icinga-0.6.21_1

[Lars Engels]

On Wed, Apr 22, 2015 at 01:53:53PM +0200, Ruud Boon wrote:
> Hi,
> 
> I’m working with icinga2 and would like to add the pnp grapher.
> Is it possible to add an option for icinga2 support. Currently when
> installing it also install icinga1.
> 
> All the best.
> Ruud

Currently, if you want to use Icinga's classic web interface with
Icinga 2, you also need Icinga 1.x port. Or don't you use this?

But I can take a look if it's possible for pnp to optionally depend on Icinga 2.


pgp4XG6b_Exue.pgp
Description: PGP signature

Re: FreeBSD Port: icinga2-2.3.3_1

[Lars Engels]

On Thu, Apr 23, 2015 at 05:55:37PM +0200, Ruud Boon wrote:
> Hi!
> 
> Thanks again for maintaining the freebsd ports. 
> Do you have any plans of upgrading to icinga2-2.4 soon?
> I got some issues that probably are fixed with the update.
> 

Thanks for reminding me of the new version. I just updated the port.

Lars


pgpcd0t5Qz_dw.pgp
Description: PGP signature

Re: FreeBSD Port: security/samhain

[Lars Engels]

On Wed, Jun 10, 2015 at 11:59:02AM +0200, Ryder Dain wrote:
> Hello,
> 
> I’d really like to see this port returned to the tree, updated and
> packaged for use. It’s currently at 3.1.6, now builds with clang, and
> needs only a couple tweaks to make it FreeBSD-friendly.
> 
> Is there any chance this can happen? I’d be more than happy to take
> over port maintenance.
> 

Yes, please send patches for an updated version.


pgpVZVez74lHB.pgp
Description: PGP signature

Re: net-mgmt/pnp and nagios4

[Lars Engels]

On Fri, Jul 24, 2015 at 11:35:05AM +0200, Marko Cupać wrote:
> Hi,
> 
> Is it possible to run pnp4nagios with nagios4 on FreeBSD? I see that
> their documentation page states that "PNP4Nagios Broker Module
> npcdmod.o is not compatible with Nagios Core 4.x". However, I plan to
> use "Bulk Mode with NPCD", or maybe even Bulk or Synchronous mode.
> Those should have no problem with nagios4.
> 
> Building pnp in poudriere pulls in nagios, but I already have nagios4
> installed. Could pnp port be modified so that one can choose nagios
> version?

Hi Marko,

it would probably be possible to add a pnp-nagios4 slave port to pnp.
You could copy the pnp-icinga port and change the dependency to
net-mgmt/nagios4.

Lars


pgpPCtvSq92xr.pgp
Description: PGP signature

Re: Icinga Web 2

[Lars Engels]

On Thu, Jul 30, 2015 at 10:48:44AM +0200, Kurt Jaeger wrote:
> Hi!
> 
> > We are deploying a new monitoring host and testing Icinga2, so far it
> > looks good.
> > 
> > Although Icinga Web 2 is not yet production ready I would like to know
> > if there are plans to make a port for it in due time? I am trying it out
> > now and apart from changing a myriad of paths it should not be difficult.
> 
> If you can provide a rough draft of a port, I'd look into it.

I managed to run a previous snapshot from git. But it's a bit hackish,
not well documented and you need to change a bit of the paths. If time
permits I'll make a port of it.


pgps_TYjAwt7R.pgp
Description: PGP signature

Re: icingaweb2 port ?

[Lars Engels]

On Sun, Oct 04, 2015 at 02:27:53PM +0200, Kurt Jaeger wrote:
> Hi!
> 
> Is anyone working on an icingaweb2 port, now that they released 2.0.0 ?
> 
> https://github.com/Icinga/icingaweb2

Yes, I do.

Installing it manually already works, now I need to create a port.


pgpgMMNoahUvQ.pgp
Description: PGP signature

Re: icingaweb2 port ?

[Lars Engels]

On Mon, Oct 05, 2015 at 01:14:01PM +0200, Lars Engels wrote:
> On Sun, Oct 04, 2015 at 02:27:53PM +0200, Kurt Jaeger wrote:
> > Hi!
> > 
> > Is anyone working on an icingaweb2 port, now that they released 2.0.0 ?
> > 
> > https://github.com/Icinga/icingaweb2
> 
> Yes, I do.
> 
> Installing it manually already works, now I need to create a port.


Done: http://www.freshports.org/net-mgmt/icingaweb2


pgpDlKvoIlobI.pgp
Description: PGP signature

Re: distfiles cleaner

[Lars Engels]

On Mon, Oct 19, 2015 at 02:16:37PM +0200, Julian H. Stacey wrote:
> Hi ports@
> What is the modern equivalent of this obsolete stuff please ?
> 
> http://www.freebsd.org/cgi/man.cgi?query=portsclean&sektion=1&apropos=0&manpath=FreeBSD+9.0-RELEASE+and+Ports
>   portsclean --distclean
>   Clean out all the distfiles that are not referenced by any
>   port in the ports tree.
> 
> https://wiki.freebsd.org/portupgrade
>   Portupgrade (aka pkgtools)
>   last edited 2012-08-01

Try distviper from sysutils/bsdadminscripts.


pgpK3VsjPGPwL.pgp
Description: PGP signature

security/vpnc: Redistribution is not allowed if linked against OpenSSL

[Lars Engels]

The vpnc port has the following:


LEGAL_TEXT= Redistribution is not allowed if linked against OpenSSL

.if ${PORT_OPTIONS:MSSL}
NO_PACKAGE= binary linked against OpenSSL must not be redistributed
CFLAGS+=-DOPENSSL_GPL_VIOLATION


Could anyone explain why this is an issue?



pgpDIGYBIe6Ou.pgp
Description: PGP signature

Re: pkg : option to exclude some files from checksum ?

[Lars Engels]

On Mon, Nov 02, 2015 at 12:35:10AM +0100, Xavier wrote:
> Hi folks,
> 
> I noticed that some ports are complaining in daily check that a checksum 
> has changed.
> 
> Example : f-prot which checksums virus definitions, which obviously changes.
> 
> Is there some macro/option in Makefile to not checksum this file ?
> 
> I hope my point is clear enough...
> 
> TIA,
> 
> Xav

make -DNO_CHECKSUM should work


pgpjnxgal6Wn1.pgp
Description: PGP signature

Re: Removing documentation

[Lars Engels]

My rather short experience:

Synth configuration profile: LiveSystem
===
   [A] Ports directory/usr/ports
   [B] Packages directory /var/synth/live_packages
   [C] Distfiles directory/usr/ports/distfiles
   [D] Port options directory /var/db/ports
   [E] Build logs directory   /var/log/synth
   [F] Build base directory   /usr/obj/synth-live
   [G] System root directory  /
   [H] Compiler cache directory   disabled
   [I] Num. concurrent builders   6
   [J] Max. jobs per builder  4
   [K] Use tmpfs for work areatrue
   [L] Use tmpfs for /usr/local   true
   [M] Display using ncurses  true
   [N] Fetch prebuilt packagestrue

   [>]   Switch/create profiles
   [RET] Exit

Press key of selection:
root@fbsd01:~ # synth status
Querying system about current package installations.
Stand by, comparing installed packages against the ports tree.
Stand by, building pkg(8) first ... Failed!!  (Synth must exit)
Unfortunately, the system upgrade failed.
root@fbsd01:~ # uname -a
FreeBSD fbsd01 10.2-RELEASE-p9 FreeBSD 10.2-RELEASE-p9 #0: Thu Jan 14 01:32:46 
UTC 2016 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  
amd64
root@fbsd01:~ #


Not a very verbose message why it actually failed.
I need a proxy server to access the internet. Could this be the problem?
*_[pP][rR][oO][xX][yY] env vars are all set, though.


pgpCiYdOtis8M.pgp
Description: PGP signature