FreeBSD ports you maintain which are out of date

2014-07-18 Thread portscout 
Dear port maintainer,

The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you can
safely ignore the entry.

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

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


Port| Current version | New version
+-+
astro/py-pyfits | 3.1.2   | 3.3
+-+
audio/rioutil   | 1.5.0   | 1.5.0br3
+-+
biology/libsbml | 5.10.0  | 5.10.2
+-+
databases/geoserver-mysql-plugin| 2.1.1   | 2.5.1
+-+
graphics/geoserver  | 2.1.1   | 2.5.1
+-+
net/py-xmlrpc   | 0.8.8.3 | 0.9
+-+
print/hyperlatex| 2.9a| 2.9
+-+
science/jmol| 13.2.3  | 14.1.17
+-+
security/fswatch| 0.02beta5   | 0.02.04beta
+-+
www/groupoffice | 3.7.24  | 6.0.5
+-+


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

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

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

When poudriere jails become stuck in a loop

2014-07-18 Thread Beeblebrox 
I have observed that some poudriere jails, on occasion, get stuck in a
hanging pattern. If I go to a jail that became stuck, top always shows
something like:

PID USERNAME THR PRI NICE SIZE RES STATE   C   TIMEWCPU COMMAND
91534 root 1  233 21840K  2376K CPU33   0:00   0.02% top
24713 root 1  523 49828K 0K wait2   0:13   0.00% 
24637 root 1  233  9048K   148K wait0   0:00   0.00% make
26552 root 1  523   190M44K urdlck  0   0:00   0.00% dot
24652 root 1  523 16988K 0K wait1   0:00   0.00% 
26551 root 1  523 16988K 0K wait3   0:00   0.00% 

The solution I have found is to kill the process named "dot" (26552 in this
case). Poudriere then picks up from where it left off and successfully
completes the package build.

Regards.



-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/When-poudriere-jails-become-stuck-in-a-loop-tp5929736.html
Sent from the freebsd-ports mailing list archive at Nabble.com.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

/usr/local/share/poudriere/include/common.sh.freebsd: sysctl: not found

2014-07-18 Thread Anton Shterenlikht 
I can run this command interactively:

/usr/local/bin/poudriere bulk -J4 -j ia64-10 -f 
/usr/local/etc/poudriere.d/pkglist

and build the packages.

But when I put in into crontab, I get:

/usr/local/share/poudriere/include/common.sh.freebsd: sysctl: not found

and package building does not start.

Please advise.

This is 10.0-STABLE #0 r268571 ia64.

# pkg info -xo poud
poudriere-devel-3.0.99.20140626 ports-mgmt/poudriere-devel
# 

Thanks

Anton

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

Managing multiple repos with Portshaker/Poudriere

2014-07-18 Thread Rick Miller 
Hi all,

I intend to utilize Poudriere to build binary packages for FreeBSD.  The
initial design includes a private git repo which tracks FreeBSD Ports (from
gthub) in a pristine branch.  Changes to this pristine branch are merged
into another branch which, in addition to the official ports tree, includes
a custom category where private ports are committed.  A major advantage
here is the ability to tag the repo according to OS releases.

While planning the deployment of such a strategy, I happened upon a blog
post[1] describing a workflow for managing this utilizing portshaker and
poudriere to combine the remote freebsd ports tree with an internal private
repo.  The method described here is appealing as it removes the need to
track freebsd-ports internally, but would I then lose the ability to tag
specific commits which would be tied to OS releases?

[1]
http://funcptr.net/2013/12/11/building-custom-ports-with-poudriere-and-portshaker/

-- 
Take care
Rick Miller
___
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: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?

2014-07-18 Thread Lars Engels 
On Thu, Jul 17, 2014 at 01:00:03PM -0700, Adrian Chadd wrote:
> On 17 July 2014 12:57, Andreas Nilsson  wrote:
> >
> >
> >
> > On Thu, Jul 17, 2014 at 9:28 PM, Adrian Chadd  wrote:
> >>
> >> Hi!
> >>
> >> 3) The binary packages need to work out of the box
> >> 4) .. which means, when you do things like pkg install apache, it
> >> can't just be installed and not be enabled, because that's a bit of a
> >> problem;
> >
> > I disagree on this. For network services on linux ( apart from ssh ), I want
> > that started very seldom. But I do want the package installed so that when I
> > need it, it is there. Having it autostart as part of being installed is
> > breaking KISS and in some way unix philosophy: I asked for something to be
> > installed, not installed and autostarted.
> 
> That's cool. We can disagree on that. But the fact that you have to
> edit a file to enable things and hope you get the right start entry in
> /etc/rc.conf or /usr/local/etc/rc.conf, or wherever you put it is, is
> a pain.

No, Sir! No need to edit anything:

root@testjail: # pkg install apache24
Updating repository catalogue
The following 5 packages will be installed:

Installing pcre: 8.33
Installing gdbm: 1.10
Installing db42: 4.2.52_5
Installing apr: 1.4.8.1.5.3
Installing apache24: 2.4.6_1

The installation will require 47 MB more space

5 MB to be downloaded

Proceed with installing packages [y/N]: y
gdbm-1.10.txz 100%   83KB  83.2KB/s  83.2KB/s   00:00
db42-4.2.52_5.txz 100% 1457KB   1.4MB/s   1.4MB/s   00:00
apr-1.4.8.1.5.3.txz 100%  390KB 389.5KB/s 389.5KB/s   00:00
apache24-2.4.6_1.txz 100% 3649KB   3.6MB/s   3.6MB/s   00:00
Checking integrity... done
[1/5] Installing pcre-8.33... done
[2/5] Installing gdbm-1.10... done
[3/5] Installing db42-4.2.52_5... done
[4/5] Installing apr-1.4.8.1.5.3... done
[5/5] Installing apache24-2.4.6_1...===> Creating users and/or groups.
Using existing group 'www'.
Using existing user 'www'.
/usr/local/share/examples/apache24/httpd.conf ->
/usr/local/etc/apache24/httpd.conf
 done
To run apache www server from startup, add apache24_enable="yes"
in your /etc/rc.conf. Extra options can be found in startup script.

Your hostname must be resolvable using at least 1 mechanism in
/etc/nsswitch.conf typically DNS or /etc/hosts or apache might
have issues starting depending on the modules you are using.

root@testjail: # sysrc apache24_enable=yes
apache24_enable:  -> yes

root@testjail: # service apache24 start
Performing sanity check on apache24 configuration:
AH00557: httpd: apr_sockaddr_info_get() failed for testjail
AH00558: httpd: Could not reliably determine the server's fully
qualified domain name, using 127.0.0.1. Set the 'ServerName' directive
globally to suppress this message
Syntax OK
Starting apache24.
AH00557: httpd: apr_sockaddr_info_get() failed for testjail
AH00558: httpd: Could not reliably determine the server's fully
qualified domain name, using 127.0.0.1. Set the 'ServerName' directive
globally to suppress this message
root@testjail: #


That's 3 commands to enter. Admittedly 2 more than on some OS that
blindly starts any service you install, but 2 steps more logical and
even a newbie can do this.

What could be done is that pkg looks for rc scripts in a package,
extracts the enable line and prints a message how to enable the script /
daemon permanently.

Like: 
- To start the script "apache24" once run "service apache24 onestart".
- To start the script "apache24" at boot time run "sysrc apache24_enable=yes"
- The script "apache24" has the following optional settings for /etc/rc.conf:
apache24_profiles (str): Set to "" by default.
 Define your profiles here.
apache24limits_enable (bool):Set to "NO" by default.
Set it to yes to run `limits $limits_args`
just before apache starts.
apache24_flags (str):Set to "" by default.
Extra flags passed to start command.
apache24limits_args (str):   Default to "-e -C daemon"
Arguments of pre-start limits run.
apache24_http_accept_enable (bool): Set to "NO" by default.
Set to yes to check for accf_http kernel
module on start up and load if not loaded.
apache24_fib (str): Set an altered default network view for apache





pgpIEpFVOIfJI.pgp
Description: PGP signature

Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?

2014-07-18 Thread Lars Engels 
On Fri, Jul 18, 2014 at 02:10:25PM +0200, Lars Engels wrote:
> On Thu, Jul 17, 2014 at 01:00:03PM -0700, Adrian Chadd wrote:
> > On 17 July 2014 12:57, Andreas Nilsson  wrote:
> > >
> > >
> > >
> > > On Thu, Jul 17, 2014 at 9:28 PM, Adrian Chadd  wrote:
> > >>
> > >> Hi!
> > >>
> > >> 3) The binary packages need to work out of the box
> > >> 4) .. which means, when you do things like pkg install apache, it
> > >> can't just be installed and not be enabled, because that's a bit of a
> > >> problem;
> > >
> > > I disagree on this. For network services on linux ( apart from ssh ), I 
> > > want
> > > that started very seldom. But I do want the package installed so that 
> > > when I
> > > need it, it is there. Having it autostart as part of being installed is
> > > breaking KISS and in some way unix philosophy: I asked for something to be
> > > installed, not installed and autostarted.
> > 
> > That's cool. We can disagree on that. But the fact that you have to
> > edit a file to enable things and hope you get the right start entry in
> > /etc/rc.conf or /usr/local/etc/rc.conf, or wherever you put it is, is
> > a pain.
> 
> No, Sir! No need to edit anything:
> 
> root@testjail: # pkg install apache24
> Updating repository catalogue
> The following 5 packages will be installed:
> 
> Installing pcre: 8.33
> Installing gdbm: 1.10
> Installing db42: 4.2.52_5
> Installing apr: 1.4.8.1.5.3
> Installing apache24: 2.4.6_1
> 
> The installation will require 47 MB more space
> 
> 5 MB to be downloaded
> 
> Proceed with installing packages [y/N]: y
> gdbm-1.10.txz 100%   83KB  83.2KB/s  83.2KB/s   00:00
> db42-4.2.52_5.txz 100% 1457KB   1.4MB/s   1.4MB/s   00:00
> apr-1.4.8.1.5.3.txz 100%  390KB 389.5KB/s 389.5KB/s   00:00
> apache24-2.4.6_1.txz 100% 3649KB   3.6MB/s   3.6MB/s   00:00
> Checking integrity... done
> [1/5] Installing pcre-8.33... done
> [2/5] Installing gdbm-1.10... done
> [3/5] Installing db42-4.2.52_5... done
> [4/5] Installing apr-1.4.8.1.5.3... done
> [5/5] Installing apache24-2.4.6_1...===> Creating users and/or groups.
> Using existing group 'www'.
> Using existing user 'www'.
> /usr/local/share/examples/apache24/httpd.conf ->
> /usr/local/etc/apache24/httpd.conf
>  done
> To run apache www server from startup, add apache24_enable="yes"
> in your /etc/rc.conf. Extra options can be found in startup script.
> 
> Your hostname must be resolvable using at least 1 mechanism in
> /etc/nsswitch.conf typically DNS or /etc/hosts or apache might
> have issues starting depending on the modules you are using.
> 
> root@testjail: # sysrc apache24_enable=yes
> apache24_enable:  -> yes
> 
> root@testjail: # service apache24 start
> Performing sanity check on apache24 configuration:
> AH00557: httpd: apr_sockaddr_info_get() failed for testjail
> AH00558: httpd: Could not reliably determine the server's fully
> qualified domain name, using 127.0.0.1. Set the 'ServerName' directive
> globally to suppress this message
> Syntax OK
> Starting apache24.
> AH00557: httpd: apr_sockaddr_info_get() failed for testjail
> AH00558: httpd: Could not reliably determine the server's fully
> qualified domain name, using 127.0.0.1. Set the 'ServerName' directive
> globally to suppress this message
> root@testjail: #
> 
> 
> That's 3 commands to enter. Admittedly 2 more than on some OS that
> blindly starts any service you install, but 2 steps more logical and
> even a newbie can do this.
> 
> What could be done is that pkg looks for rc scripts in a package,
> extracts the enable line and prints a message how to enable the script /
> daemon permanently.
> 
> Like: 
> - To start the script "apache24" once run "service apache24 onestart".
> - To start the script "apache24" at boot time run "sysrc apache24_enable=yes"
> - The script "apache24" has the following optional settings for /etc/rc.conf:
> apache24_profiles (str): Set to "" by default.
>  Define your profiles here.
> apache24limits_enable (bool):Set to "NO" by default.
> Set it to yes to run `limits $limits_args`
> just before apache starts.
> apache24_flags (str):Set to "" by default.
> Extra flags passed to start command.
> apache24limits_args (str):   Default to "-e -C daemon"
> Arguments of pre-start limits run.
> apache24_http_accept_enable (bool): Set to "NO" by default.
> Set to yes to check for accf_http kernel
> module on start up and load if not loaded.
> apache24_fib (str): Set an altered default network view for apache
> 
> 
> 

Sorry for no reading the whole thread first. This was already suggested
in another part of the thread.


pgp5bG5Xyw8GZ.pgp
Description: PGP signature

Re: /usr/local/share/poudriere/include/common.sh.freebsd: sysctl: not found

2014-07-18 Thread Guido Falsi 
On 07/18/14 12:01, Anton Shterenlikht wrote:
> I can run this command interactively:
> 
> /usr/local/bin/poudriere bulk -J4 -j ia64-10 -f 
> /usr/local/etc/poudriere.d/pkglist
> 
> and build the packages.
> 
> But when I put in into crontab, I get:
> 
> /usr/local/share/poudriere/include/common.sh.freebsd: sysctl: not found
> 
> and package building does not start.

Looks like a PATH problem.

Does your crontab PATH include /sbin?

-- 
Guido Falsi 
___
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: /usr/local/share/poudriere/include/common.sh.freebsd: sysctl: not found

2014-07-18 Thread Anton Shterenlikht 
>From m...@madpilot.net Fri Jul 18 14:02:57 2014
>
>Looks like a PATH problem.
>
>Does your crontab PATH include /sbin?

forgot about it, my bad.

Thanks

Anton

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

Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?

2014-07-18 Thread Dreamcat4 
On Thu, Jul 17, 2014 at 7:25 PM, Craig Rodrigues 
wrote:

> Hi,
>
> I attend a lot of different Meetup groups in the San Francisco Bay Area /
> Silicon Valley.
>
> What I am seeing is the following usage pattern for new developers,
> especially for web apps and cloud applications.
>
> (1)   On their desktop/laptop, they will generally be using
>a Mac running OS X.  This is their desktop Unix environment.
>This seems to be true of almost 90% of the people that I meet.
>The 10% of people who run a PC laptop, will mostly be running
> Windows.  Very few seem to run Linux on their laptops, but
>if they do, it will likely be Ubuntu Linux.
>
> (2)  For their deployed application, generally they will deploy to
>   a Linux environment on a server.  These days, the server will
>   very likely be in a cloud environment:  Amazon, Rackspace,
>   Heroku.
>
>
> For (1), encouraging people to move away from a Mac to FreeBSD for their
> desktop environment is a tough sell.  Apple is a multi-billion dollar
> company, and they make beautiful hardware, and software with
> a fantastic end-user experience.  The PC-BSD project is fighting the
> good fight in terms of making a usable FreeBSD desktop, but its
> a touch battle to fight.
>
> For (2), encouraging people to move away from Linux to FreeBSD
> on the server, may be something where we can get more wins.
> I think we can do this by having more HOWTO articles on
> the FreeBSD web page that explain the following:
>
>
> (1)  We need a HOWTO article that explains for each command using apt
> or yum for installing packages,
>   how can I do the same thing using "pkg".
>   Even if we have a web page with a table, contrasting the
>   apt/yum commands, and pkg commands, that would be super
>   useful.
>
>   A lot of folks have moved away from FreeBSD, purely because
>   they are sick of pkg_add.  We need to explain to folks that
>   we have something better, that is quite competitive to
>   apt/yum, and it is easy to use.
>
>  (2)  We need a HOWTO article that explains how to set up
>a FreeBSD environment with some of the major cloud providers,
>i.e. Amazon, Rackspace, Microsoft Azure, etc.
>
>
> Do we have such articles today, or is anybody working on something
> like that?
>

I haven't such specific articles. However I did create a project which lets
people more easily install and 'try out' FreeBSD. It runs ontop of either
FreeNAS, pfSense or NAS4Free.

The idea is that because you can boot those distress off of a USB stick,
(it's like a liveCD). However you can then install the full FreeBSD generic
onto any suitably-formatted attached hard disk. (including PKGNG and ports
tree).

None of my documentation is aimed specifically at linux -> FreeBSD. However
I can say that it's utterly true (if you have Mac OS X). The desktop
experience is definately nicer (much less niggly / annoying problems).

And on Macs we have "brew install"… which is "allright". But you can't use
Macs as effectively for server stuff. It doesn't really "feel right" for
that purpose. And homebrew is like ports or gentoo (compiles everything, no
binary packages).

For me, the FreeBSD is what I decide to for server (more than linux) *not
just only* for PKGNG. We are glad that is here now. But also (very
important). If FreeBSD jails. Which isn't "as-good-as", but often superior
to such linux equivalent (if any). In terms of both security, and
efficiency.

Here you can see my FreeBSD jails HowTo:

http://dreamcat4.github.io/finch/jails-how-to/

Which is as simple as I could ever be able to make it.

Sorry I don't have any other ideas in regards to how to address the
overwhelming popularity of Linux over FreeBSD. It often isn't justified.
However in some ways linux is like windows now. For example with
overwhelming hardware support (that sometimes is not as good on FreeBSD).

And Linux is more success on embedded because it can run on many different
kinds of CPUs. Wheras FreeBSD isn't very much support for embedded CPU
(unless they happen to be X86). I get the (maybe not justified) impression
that even ARM isn't so well supported on FreeBSD.

Some things you can't change with just only a better "How-To". Even if
FreeBSD is super-great / rocks so well now.

I think if we had these two HOWTO articles today, and we could
> aggressively point people at them, this would be a huge win
> for expanding the number of people who try out FreeBSD
> for modern server applications.
>
> --
> Craig
> ___
> 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

Re: When poudriere jails become stuck in a loop

2014-07-18 Thread Patrick Powell 

On 07/18/14 02:41, Beeblebrox wrote:

I have observed that some poudriere jails, on occasion, get stuck in a
hanging pattern. If I go to a jail that became stuck, top always shows
something like:

PID USERNAME THR PRI NICE SIZE RES STATE   C   TIMEWCPU COMMAND
91534 root 1  233 21840K  2376K CPU33   0:00   0.02% top
24713 root 1  523 49828K 0K wait2   0:13   0.00% 
24637 root 1  233  9048K   148K wait0   0:00   0.00% make
26552 root 1  523   190M44K urdlck  0   0:00   0.00% dot
24652 root 1  523 16988K 0K wait1   0:00   0.00% 
26551 root 1  523 16988K 0K wait3   0:00   0.00% 

The solution I have found is to kill the process named "dot" (26552 in this
case). Poudriere then picks up from where it left off and successfully
completes the package build.

Regards.



-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/When-poudriere-jails-become-stuck-in-a-loop-tp5929736.html
Sent from the freebsd-ports mailing list archive at Nabble.com.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"



I think I have observed the same issue.  When you say 'go to a jail' 
what did you do to see

this information?  I get a lot of other info that clouds the issue.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: When poudriere jails become stuck in a loop

2014-07-18 Thread Beeblebrox 
@Patrick:

1. During poudriere run, do  to display jails which have been
running for obviously too long. Note the poudriere run number - lets say #4
has been running for 2+ hours for an obviously small port.
2. "# jls" and note the jail ID for poudriere_#4. There will be two jails
for each process, the one with 127.0.0.1 IP is the real build environment -
lets say jail_ID is 20.
3. "# jexec 20 top" will give you the running processes in that build jail.
If you see the "dot" item, I guarantee you that jail is stuck.

Regards.



-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/When-poudriere-jails-become-stuck-in-a-loop-tp5929736p5929843.html
Sent from the freebsd-ports mailing list archive at Nabble.com.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?

2014-07-18 Thread Dreamcat4 
On Thu, Jul 17, 2014 at 9:54 PM, Baptiste Daroussin 
wrote:

> On Thu, Jul 17, 2014 at 10:21:17PM +0200, Andreas Nilsson wrote:
> > On Thu, Jul 17, 2014 at 10:15 PM, Navdeep Parhar 
> wrote:
> >
> > > On 07/17/14 13:12, Adrian Chadd wrote:
> > > > On 17 July 2014 13:03, Alberto Mijares  wrote:
> > > >> On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd 
> > > wrote:
> > > >>> Hi!
> > > >>>
> > > >>> 3) The binary packages need to work out of the box
> > > >>> 4) .. which means, when you do things like pkg install apache, it
> > > >>> can't just be installed and not be enabled, because that's a bit
> of a
> > > >>> problem;
> > > >>
> > > >>
> > > >> No. Please NEVER do that! The user must be able to edit the files
> and
> > > >> start the service by himself.
> > > >
> > > > Cool, so what's the single line command needed to type in to start a
> > > > given package service?
> > >
> > > Aren't sysrc(8) and service(8) for this kind of stuff?
> > >
> >
> > They sure are.
> >
> > Well, pkg install $service ; sysrc ${service}_enable="YES" would do.
> > Although some services have different names than the packge, which is
> sort
> > of annoying.
>
> Maybe service needs to be extended (seriously sysrc
> ${service}_enable="YES" is
> not user friendly) we have service -l that list the services, maybe a
> service
>

This might be a pretty good idea. (barring technical obstacles).


> ${service} on that create /etc/rc.conf.d/${service} with
> ${service}_enable="YES"
> in it and service ${service} off to remove it
>

I think we should hope for an API / service interface that can try to avoid
(as much as it can) to require specifically "rc.conf" file and no other
possible way. Because FreeBSD may replace the current rc.d system in future
with something else better / next generation. For example the on-going
openlaunchd project. That question is more about "when" rather than "if".

maybe service -l could also be extended to show the current status (maybe
> with a
> -v switch)
>
> but for sure having the service off by default is a good idea :)
>

It wouldn't hurt very much to have some optional flag to the "pkg install"
command that allowed a user to do in 1 command. Then the global
configuration of services being installed "off" by default would remain as
always.

Yet allowing that little extra switch would achieve the stated goal. And
help towards FreeBSD being "a slightly more polished OS" that is more
user-friendly. Since, you know do the math. It is 1 fewer total commands to
type in. Such savings "all adds up". If enough such minor improvement can
be made all across the board. Then it makes a difference.


>
> regards,
> Bapt
>
___
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: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?

2014-07-18 Thread Lars Engels 
On Thu, Jul 17, 2014 at 10:21:17PM +0200, Andreas Nilsson wrote:
> On Thu, Jul 17, 2014 at 10:15 PM, Navdeep Parhar  wrote:
> 
> > On 07/17/14 13:12, Adrian Chadd wrote:
> > > On 17 July 2014 13:03, Alberto Mijares  wrote:
> > >> On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd 
> > wrote:
> > >>> Hi!
> > >>>
> > >>> 3) The binary packages need to work out of the box
> > >>> 4) .. which means, when you do things like pkg install apache, it
> > >>> can't just be installed and not be enabled, because that's a bit of a
> > >>> problem;
> > >>
> > >>
> > >> No. Please NEVER do that! The user must be able to edit the files and
> > >> start the service by himself.
> > >
> > > Cool, so what's the single line command needed to type in to start a
> > > given package service?
> >
> > Aren't sysrc(8) and service(8) for this kind of stuff?
> >
> 
> They sure are.
> 
> Well, pkg install $service ; sysrc ${service}_enable="YES" would do.
> Although some services have different names than the packge, which is sort
> of annoying.

I hacked up a solution for service(8):

http://bsd-geek.de/FreeBSD/service.sh.enable-disable.patch

The patch adds the following directives to service(8):

enable: Grabs an rc script's rcvar value and runs "sysrc foo_enable=YES"
disable: The opposite of enable
rcdelete: Deletes an rc script's rcvar value from /etc/rc.conf using
  "sysrc -x foo_enable"

The nice thing about is that you can use one of the new directives on
one line with the old ones, as long as the new are the first argument:

# service syslogd enable
# service apache24 disable stop
# service apache24 rcdelete stop
# service nginx enable start


So after installing a package, to start and enable a daemon permanently
all you have to run is
# service foo enable start

Lars

P.S.: Thansk to Devin for his hard work on sysrc!


pgpXcgD203Myq.pgp
Description: PGP signature

Re: When poudriere jails become stuck in a loop

2014-07-18 Thread Beeblebrox 
It just occurred to me that I should mention I use core unlocking. My
CPU: AMD-AthlonII-X3-460, with 4th core unlocked making it an X4-460.

On the other hand, I have seen two poudriere jails stuck in loops at
the same time (out of running 4), which may not mean much since
instructions from jail are picked up by any available core.

Something else I have noticed lately is that my 4G swap keeps running
out of space: "swap_pager_getswapspace(4): failed". This is probably a
result of the stuck jail and not a cause IMHO.




-
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/When-poudriere-jails-become-stuck-in-a-loop-tp5929736p5929861.html
Sent from the freebsd-ports mailing list archive at Nabble.com.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?

2014-07-18 Thread Brooks Davis 
On Thu, Jul 17, 2014 at 11:07:39PM +0200, Baptiste Daroussin wrote:
> On Thu, Jul 17, 2014 at 01:57:52PM -0700, Adrian Chadd wrote:
> > On 17 July 2014 13:54, Baptiste Daroussin  wrote:
> > > On Thu, Jul 17, 2014 at 10:21:17PM +0200, Andreas Nilsson wrote:
> > >> On Thu, Jul 17, 2014 at 10:15 PM, Navdeep Parhar  
> > >> wrote:
> > >>
> > >> > On 07/17/14 13:12, Adrian Chadd wrote:
> > >> > > On 17 July 2014 13:03, Alberto Mijares  wrote:
> > >> > >> On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd 
> > >> > wrote:
> > >> > >>> Hi!
> > >> > >>>
> > >> > >>> 3) The binary packages need to work out of the box
> > >> > >>> 4) .. which means, when you do things like pkg install apache, it
> > >> > >>> can't just be installed and not be enabled, because that's a bit 
> > >> > >>> of a
> > >> > >>> problem;
> > >> > >>
> > >> > >>
> > >> > >> No. Please NEVER do that! The user must be able to edit the files 
> > >> > >> and
> > >> > >> start the service by himself.
> > >> > >
> > >> > > Cool, so what's the single line command needed to type in to start a
> > >> > > given package service?
> > >> >
> > >> > Aren't sysrc(8) and service(8) for this kind of stuff?
> > >> >
> > >>
> > >> They sure are.
> > >>
> > >> Well, pkg install $service ; sysrc ${service}_enable="YES" would do.
> > >> Although some services have different names than the packge, which is 
> > >> sort
> > >> of annoying.
> > >
> > > Maybe service needs to be extended (seriously sysrc 
> > > ${service}_enable="YES" is
> > > not user friendly) we have service -l that list the services, maybe a 
> > > service
> > > ${service} on that create /etc/rc.conf.d/${service} with 
> > > ${service}_enable="YES"
> > > in it and service ${service} off to remove it
> > >
> > > maybe service -l could also be extended to show the current status (maybe 
> > > with a
> > > -v switch)
> > >
> > > but for sure having the service off by default is a good idea :)
> > 
> > Yeah, maybe having it populate an entry of service_enable="NO" for now .
> 
> then you need to extend rcng to support /usr/local/etc/rc.conf.d so the 
> packages
> can install them without touching base :) and we will need to wait for all
> supported FreeBSD version to have the said modification)

Here's a totally untested patch to do that.  I was rather surprised that
this wasn't configurable already.

-- Brooks

Index: defaults/rc.conf
===
--- defaults/rc.conf(revision 268825)
+++ defaults/rc.conf(working copy)
@@ -56,6 +56,7 @@
 local_startup="/usr/local/etc/rc.d" # startup script dirs.
 script_name_sep=" "# Change if your startup scripts' names contain spaces
 rc_conf_files="/etc/rc.conf /etc/rc.conf.local"
+rc_conf_dirs="/etc/rc.conf.d /usr/local/etc/rc.conf.d"
 
 # ZFS support
 zfs_enable="NO"# Set to YES to automatically mount ZFS file 
systems
Index: rc.subr
===
--- rc.subr (revision 268825)
+++ rc.subr (working copy)
@@ -1289,10 +1289,12 @@
fi
_rc_conf_loaded=true
fi
-   if [ -f /etc/rc.conf.d/"$_name" ]; then
-   debug "Sourcing /etc/rc.conf.d/${_name}"
-   . /etc/rc.conf.d/"$_name"
-   fi
+   for _dir in ${rc_conf_dirs}; do
+   if [ -f "$_dir"/"$_name" ]; then
+   debug "Sourcing ${_dir}/${_name}"
+   . "$dir"/"$_name"
+   fi
+   done
 
# Set defaults if defined.
for _var in $rcvar; do


pgp70OxID1KyT.pgp
Description: PGP signature

Using WANT_PHP_WEB

2014-07-18 Thread Matthew Pounsett 

I’m trying to compile a port that sets WANT_PHP_WEB=yes.  The docs say this 
tells the ports system to compile either the PHP CGI or mod_php port.  My 
question is.. how does the ports system get directed to one or the other?  As 
the person compiling this port I’d like it to use mod_php, but it’s not getting 
built or included in the dependencies, and I can’t find any documentation about 
how to give it a hint.

Without a knob in place to direct this one way or the other, I’m not 
understanding why WANT_PHP_WEB exists .. why not just have the port maintainer 
set either _CGI or _MOD?


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

websieve.pl System Error

2014-07-18 Thread Janos Dohanics 
Hello List,

I'm trying to make webmail.pl work, and so far, no luck. Here is what I
have:

FreeBSD 9.2-STABLE #0 r264952 amd64
apache22-2.2.27_4
cyrus-imapd24-2.4.17_5
cyrus-sasl-2.1.26_7
cyrus-sasl-saslauthd-2.1.26
perl5-5.16.3_11
websieve-0.63.a_1

Saslauthd is used for authentication.

Sieve/sieveshell seems to be working:

# sieveshell -a mcsmith -u mcsmith localhost
connecting to localhost
Please enter your password: 
> 

When I try to log in to "Local server" using the web interface, I get:

System Error:
User server=yourmailhost

The apache log shows error messages like:

websieve.pl: defined(%hash) is deprecated
at /usr/local/www/apache22/cgi-bin/websieve.pl line 799.

websieve.pl: \t(Maybe you should just omit the defined()?)

websieve.pl: Name "main::serverdisplay" used only once: possible typo
at /usr/local/www/apache22/cgi-bin/websieve.pl line 622.

Admin.pm: Use of uninitialized value in subroutine entry
at /usr/local/lib/perl5/site_perl/5.16/mach/Cyrus/IMAP/Admin.pm line
109.

Admin.pm: \t(in cleanup) client is not of type Cyrus::IMAP
at /usr/local/lib/perl5/site_perl/5.16/mach/Cyrus/IMAP/Admin.pm line
109.

This last one "client is not of type Cyrus::IMAP" looks a bit
worrying...

However, I can find no trace of the failed login attempt in the log
files.

/usr/local/etc/websieve/websieve.conf:

$imapserver='mail.myserver.com';
$sieveport='4190';
$imapport='143';
$maildomain='myserver.com' ;
$mailhostappend="mail.$maildomain";

%server_hosts=(
"yourmailhost"=>['Local
Server','143','4190','myserver.com','mail.myserver.com'],
);

Would you please advise?

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

[QAT] 361962: 4x leftovers, 2x finished, 2x ignored: this port requires sse2, and benefits from sse3 -- set cputype appropriately, 76x success

2014-07-18 Thread Ports-QAT 
Add DOCS to OPTIONS_DEFINE to ports that check for PORT_OPTIONS:MDOCS.
-

  Build ID:  20140715162400-56588
  Job owner: ad...@freebsd.org
  Buildtime: 3 days
  Enddate:   Fri, 18 Jul 2014 15:50:07 GMT

  Revision:  361962
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=361962

-

Port:math/R 3.0.2_2

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140715162400-56588-377282/R-3.0.2_2.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140715162400-56588-377283/R-3.0.2_2.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140715162400-56588-377284/R-3.0.2_2.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140715162400-56588-377285/R-3.0.2_2.log

-

Port:math/arpack-ng 3.1.5

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140715162400-56588-377286/arpack-ng-3.1.5.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140715162400-56588-377287/arpack-ng-3.1.5.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140715162400-56588-377288/arpack-ng-3.1.5.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140715162400-56588-377289/arpack-ng-3.1.5.log

-

Port:math/cblas 1.0_2

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140715162400-56588-377290/cblas-1.0_2.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140715162400-56588-377291/cblas-1.0_2.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140715162400-56588-377292/cblas-1.0_2.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140715162400-56588-377293/cblas-1.0_2.log

-

Port:math/crlibm 1.0.b4_1

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140715162400-56588-377294/crlibm-1.0.b4_1.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140715162400-56588-377295/crlibm-1.0.b4_1.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140715162400-56588-377296/crlibm-1.0.b4_1.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140715162400-56588-377297/crlibm-1.0.b4_1.log

-

Port:math/glpk 4.52.1_1

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140715162400-56588-377298/glpk-4.52.1_1.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140715162400-56588-377299/glpk-4.52.1_1.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140715162400-56588-377300/glpk-4.52.1_1.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140715162400-56588-377301/glpk-4.52.1_1.log

-

Port:math/kktdirect 0.5_2

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140715162400-56588-377302/kktdirect-0.5_2.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140715162400-56588-377303/kktdirect-0.5_2.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~ad...@freebsd.org/20140715162400-56588-377304/kktdirect-0.5_2.log

  Buildgroup: 9.2-QAT/i386

Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?

2014-07-18 Thread Adrian Chadd 
Hi!


On 18 July 2014 07:28, Lars Engels  wrote:
> On Thu, Jul 17, 2014 at 10:21:17PM +0200, Andreas Nilsson wrote:
>> On Thu, Jul 17, 2014 at 10:15 PM, Navdeep Parhar  wrote:
>>
>> > On 07/17/14 13:12, Adrian Chadd wrote:
>> > > On 17 July 2014 13:03, Alberto Mijares  wrote:
>> > >> On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd 
>> > wrote:
>> > >>> Hi!
>> > >>>
>> > >>> 3) The binary packages need to work out of the box
>> > >>> 4) .. which means, when you do things like pkg install apache, it
>> > >>> can't just be installed and not be enabled, because that's a bit of a
>> > >>> problem;
>> > >>
>> > >>
>> > >> No. Please NEVER do that! The user must be able to edit the files and
>> > >> start the service by himself.
>> > >
>> > > Cool, so what's the single line command needed to type in to start a
>> > > given package service?
>> >
>> > Aren't sysrc(8) and service(8) for this kind of stuff?
>> >
>>
>> They sure are.
>>
>> Well, pkg install $service ; sysrc ${service}_enable="YES" would do.
>> Although some services have different names than the packge, which is sort
>> of annoying.
>
> I hacked up a solution for service(8):
>
> http://bsd-geek.de/FreeBSD/service.sh.enable-disable.patch
>
> The patch adds the following directives to service(8):
>
> enable: Grabs an rc script's rcvar value and runs "sysrc foo_enable=YES"
> disable: The opposite of enable
> rcdelete: Deletes an rc script's rcvar value from /etc/rc.conf using
>   "sysrc -x foo_enable"
>
> The nice thing about is that you can use one of the new directives on
> one line with the old ones, as long as the new are the first argument:
>
> # service syslogd enable
> # service apache24 disable stop
> # service apache24 rcdelete stop
> # service nginx enable start
>
>
> So after installing a package, to start and enable a daemon permanently
> all you have to run is
> # service foo enable start
>
> Lars
>
> P.S.: Thansk to Devin for his hard work on sysrc!

Having a way for sysrc and service to know what particular options and
services are exposed by a given package or installed "thing" would be
nice. Right now the namespace is very flat and it's not obvious in all
instances what needs to happen to make it useful and what the options
are.

"Oh, hm, I'd like to know what options there are for controlling the
installed apache24 package, let's see"...

I remember IRIX having that command to list services, stop them and
start them, configure them enabled and disabled. Solaris grew
something like that with Solaris 10 and after the initial learning
curve it was great. Hving something like that would be 100% awesome.


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

Bug 191256

2014-07-18 Thread Jerry 
Fri, 18 Jul 2014 15:18:30 -0400

Could someone look into "Bug 191256 - [exp-run requested] security/libgcrypt:
update to 1.6.1" and possibly committing it?

Thanks!

-- 
Jerry


signature.asc
Description: PGP signature

[QAT] 362035: 2x leftovers, 2x success

2014-07-18 Thread Ports-QAT 
Update to 0.0.0.20140715 (36f63b8).
-

  Build ID:  20140716063400-21869
  Job owner: k...@freebsd.org
  Buildtime: 3 days
  Enddate:   Fri, 18 Jul 2014 20:05:46 GMT

  Revision:  362035
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=362035

-

Port:devel/go-runewidth 0.0.0.20140715

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~k...@freebsd.org/20140716063400-21869-378586/go-runewidth-0.0.0.20140715.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~k...@freebsd.org/20140716063400-21869-378587/go-runewidth-0.0.0.20140715.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~k...@freebsd.org/20140716063400-21869-378588/go-runewidth-0.0.0.20140715.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~k...@freebsd.org/20140716063400-21869-378589/go-runewidth-0.0.0.20140715.log


--
Buildarchive URL: 
redports 
___
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"

[QAT] 362037: 2x leftovers, 2x success

2014-07-18 Thread Ports-QAT 
Update to 0.0.0.20140715 (e9227d6).
-

  Build ID:  20140716064000-49328
  Job owner: k...@freebsd.org
  Buildtime: 3 days
  Enddate:   Fri, 18 Jul 2014 20:09:13 GMT

  Revision:  362037
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=362037

-

Port:devel/go-termbox 0.0.0.20140715

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~k...@freebsd.org/20140716064000-49328-378594/go-termbox-0.0.0.20140715.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~k...@freebsd.org/20140716064000-49328-378595/go-termbox-0.0.0.20140715.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~k...@freebsd.org/20140716064000-49328-378596/go-termbox-0.0.0.20140715.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~k...@freebsd.org/20140716064000-49328-378597/go-termbox-0.0.0.20140715.log


--
Buildarchive URL: 
redports 
___
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"

[QAT] 362039: 2x leftovers, 2x success

2014-07-18 Thread Ports-QAT 
Update to 0.2.1.
-

  Build ID:  20140716064400-55265
  Job owner: k...@freebsd.org
  Buildtime: 3 days
  Enddate:   Fri, 18 Jul 2014 20:10:01 GMT

  Revision:  362039
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=362039

-

Port:textproc/peco 0.2.1

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~k...@freebsd.org/20140716064400-55265-378602/peco-0.2.1.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~k...@freebsd.org/20140716064400-55265-378603/peco-0.2.1.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   SUCCESS
  Log: 
https://qat.redports.org//~k...@freebsd.org/20140716064400-55265-378604/peco-0.2.1.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~k...@freebsd.org/20140716064400-55265-378605/peco-0.2.1.log


--
Buildarchive URL: 
redports 
___
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: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?

2014-07-18 Thread Baptiste Daroussin 
On Fri, Jul 18, 2014 at 12:10:34PM -0700, Adrian Chadd wrote:
> Hi!
> 
> 
> On 18 July 2014 07:28, Lars Engels  wrote:
> > On Thu, Jul 17, 2014 at 10:21:17PM +0200, Andreas Nilsson wrote:
> >> On Thu, Jul 17, 2014 at 10:15 PM, Navdeep Parhar  wrote:
> >>
> >> > On 07/17/14 13:12, Adrian Chadd wrote:
> >> > > On 17 July 2014 13:03, Alberto Mijares  wrote:
> >> > >> On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd 
> >> > wrote:
> >> > >>> Hi!
> >> > >>>
> >> > >>> 3) The binary packages need to work out of the box
> >> > >>> 4) .. which means, when you do things like pkg install apache, it
> >> > >>> can't just be installed and not be enabled, because that's a bit of a
> >> > >>> problem;
> >> > >>
> >> > >>
> >> > >> No. Please NEVER do that! The user must be able to edit the files and
> >> > >> start the service by himself.
> >> > >
> >> > > Cool, so what's the single line command needed to type in to start a
> >> > > given package service?
> >> >
> >> > Aren't sysrc(8) and service(8) for this kind of stuff?
> >> >
> >>
> >> They sure are.
> >>
> >> Well, pkg install $service ; sysrc ${service}_enable="YES" would do.
> >> Although some services have different names than the packge, which is sort
> >> of annoying.
> >
> > I hacked up a solution for service(8):
> >
> > http://bsd-geek.de/FreeBSD/service.sh.enable-disable.patch
> >
> > The patch adds the following directives to service(8):
> >
> > enable: Grabs an rc script's rcvar value and runs "sysrc foo_enable=YES"
> > disable: The opposite of enable
> > rcdelete: Deletes an rc script's rcvar value from /etc/rc.conf using
> >   "sysrc -x foo_enable"
> >
> > The nice thing about is that you can use one of the new directives on
> > one line with the old ones, as long as the new are the first argument:
> >
> > # service syslogd enable
> > # service apache24 disable stop
> > # service apache24 rcdelete stop
> > # service nginx enable start
> >
> >
> > So after installing a package, to start and enable a daemon permanently
> > all you have to run is
> > # service foo enable start
> >
> > Lars
> >
> > P.S.: Thansk to Devin for his hard work on sysrc!
> 
> Having a way for sysrc and service to know what particular options and
> services are exposed by a given package or installed "thing" would be
> nice. Right now the namespace is very flat and it's not obvious in all
> instances what needs to happen to make it useful and what the options
> are.
> 
> "Oh, hm, I'd like to know what options there are for controlling the
> installed apache24 package, let's see"...
> 
> I remember IRIX having that command to list services, stop them and
> start them, configure them enabled and disabled. Solaris grew
> something like that with Solaris 10 and after the initial learning
> curve it was great. Hving something like that would be 100% awesome.
> 
you are asking for rcng2 with a declarative init config rather the  a script

regards,
Bapt


pgpybwPAn1ApH.pgp
Description: PGP signature

This unmaintained package will not run once built.

2014-07-18 Thread Parker Gibson 
To whom it may concern:

The port games/xtux does not run once built. The compiled binary gives a
runtime error saying something about not being able to load an adobe
Helvetica font. There is no manual page for the package and I cannot find a
configuration option for fonts.

 

root@:/usr/ports/games/xtux # work/xtux/xtux

Error loading font: -adobe-helvetica-medium-r-*-*-18-*-*-*-*-*-*-*



An error occured, please email David Lawrence 

at nogoodp...@yahoo.com with a copy of the error

messages & info about your system. Thankyou.



VERSION: XTux Arena client 20010601

OS:FreeBSD

Release: 10.0-RELEASE

Arch:amd64

Error: Font error!

(1)

Exit called in win.c, line: 636

 

Respectfully,

Parker Philip Gibson

1704 ½ South Whittier Avenue,

Springfield, Illinios 62704-4022

Phone: (801) 512-7999

E-Mail: pgib...@sdf.org

 



smime.p7s
Description: S/MIME cryptographic signature

Re: This unmaintained package will not run once built.

2014-07-18 Thread Michael Gmelin 


> On 19 Jul 2014, at 00:20, "Parker Gibson"  wrote:
> 
> To whom it may concern:
> 
> The port games/xtux does not run once built. The compiled binary gives a
> runtime error saying something about not being able to load an adobe
> Helvetica font. There is no manual page for the package and I cannot find a
> configuration option for fonts.
> 
> 
> 
> root@:/usr/ports/games/xtux # work/xtux/xtux
> 
> Error loading font: -adobe-helvetica-medium-r-*-*-18-*-*-*-*-*-*-*
> 
> 
> 
> An error occured, please email David Lawrence 
> 
> at nogoodp...@yahoo.com with a copy of the error
> 
> messages & info about your system. Thankyou.
> 
> 
> 
> VERSION: XTux Arena client 20010601
> 
> OS:FreeBSD
> 
> Release: 10.0-RELEASE
> 
> Arch:amd64
> 
> Error: Font error!
> 
> (1)
> 
> Exit called in win.c, line: 636
> 
> 
> 
> Respectfully,
> 
> Parker Philip Gibson
> 
> 1704 ½ South Whittier Avenue,
> 
> Springfield, Illinios 62704-4022
> 
> Phone: (801) 512-7999
> 
> E-Mail: pgib...@sdf.org
> 
> 
> 

Try installing x11-fonts/font-adobe-75dpi and/or -100dpi
___
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: Bug 191256

2014-07-18 Thread Carlos Jacobo Puga Medina 
pi@ requested an exp-run for libgcrypt-1.6.1. Note that it should be safe to 
commit if the run was successful.

Cheers,
-- 
Carlos Jacobo Puga Medina 
___
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: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?

2014-07-18 Thread Adrian Chadd 
On 18 July 2014 14:21, Baptiste Daroussin  wrote:
> On Fri, Jul 18, 2014 at 12:10:34PM -0700, Adrian Chadd wrote:
>> Hi!
>>
>>
>> On 18 July 2014 07:28, Lars Engels  wrote:
>> > On Thu, Jul 17, 2014 at 10:21:17PM +0200, Andreas Nilsson wrote:
>> >> On Thu, Jul 17, 2014 at 10:15 PM, Navdeep Parhar  
>> >> wrote:
>> >>
>> >> > On 07/17/14 13:12, Adrian Chadd wrote:
>> >> > > On 17 July 2014 13:03, Alberto Mijares  wrote:
>> >> > >> On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd 
>> >> > wrote:
>> >> > >>> Hi!
>> >> > >>>
>> >> > >>> 3) The binary packages need to work out of the box
>> >> > >>> 4) .. which means, when you do things like pkg install apache, it
>> >> > >>> can't just be installed and not be enabled, because that's a bit of 
>> >> > >>> a
>> >> > >>> problem;
>> >> > >>
>> >> > >>
>> >> > >> No. Please NEVER do that! The user must be able to edit the files and
>> >> > >> start the service by himself.
>> >> > >
>> >> > > Cool, so what's the single line command needed to type in to start a
>> >> > > given package service?
>> >> >
>> >> > Aren't sysrc(8) and service(8) for this kind of stuff?
>> >> >
>> >>
>> >> They sure are.
>> >>
>> >> Well, pkg install $service ; sysrc ${service}_enable="YES" would do.
>> >> Although some services have different names than the packge, which is sort
>> >> of annoying.
>> >
>> > I hacked up a solution for service(8):
>> >
>> > http://bsd-geek.de/FreeBSD/service.sh.enable-disable.patch
>> >
>> > The patch adds the following directives to service(8):
>> >
>> > enable: Grabs an rc script's rcvar value and runs "sysrc foo_enable=YES"
>> > disable: The opposite of enable
>> > rcdelete: Deletes an rc script's rcvar value from /etc/rc.conf using
>> >   "sysrc -x foo_enable"
>> >
>> > The nice thing about is that you can use one of the new directives on
>> > one line with the old ones, as long as the new are the first argument:
>> >
>> > # service syslogd enable
>> > # service apache24 disable stop
>> > # service apache24 rcdelete stop
>> > # service nginx enable start
>> >
>> >
>> > So after installing a package, to start and enable a daemon permanently
>> > all you have to run is
>> > # service foo enable start
>> >
>> > Lars
>> >
>> > P.S.: Thansk to Devin for his hard work on sysrc!
>>
>> Having a way for sysrc and service to know what particular options and
>> services are exposed by a given package or installed "thing" would be
>> nice. Right now the namespace is very flat and it's not obvious in all
>> instances what needs to happen to make it useful and what the options
>> are.
>>
>> "Oh, hm, I'd like to know what options there are for controlling the
>> installed apache24 package, let's see"...
>>
>> I remember IRIX having that command to list services, stop them and
>> start them, configure them enabled and disabled. Solaris grew
>> something like that with Solaris 10 and after the initial learning
>> curve it was great. Hving something like that would be 100% awesome.
>>
> you are asking for rcng2 with a declarative init config rather the  a script

It can be a series of scripts. The problem is that the namespace for
options has nothing else attached, like "Hi I'm an option that
starts/stops a service", "Hi I'm an option that's for this package",
"Hi I'm an option that's for this class of things." Right now there's
just a series of shell variables with educated guesses about what
package they're related to and what they do, rather than anything that
specifically says what they do.


-a
___
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: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?

2014-07-18 Thread Rui Paulo 
On Jul 17, 2014, at 13:00, Adrian Chadd  wrote:

> On 17 July 2014 12:57, Andreas Nilsson  wrote:
>> 
>> 
>> 
>> On Thu, Jul 17, 2014 at 9:28 PM, Adrian Chadd  wrote:
>>> 
>>> Hi!
>>> 
>>> 3) The binary packages need to work out of the box
>>> 4) .. which means, when you do things like pkg install apache, it
>>> can't just be installed and not be enabled, because that's a bit of a
>>> problem;
>> 
>> I disagree on this. For network services on linux ( apart from ssh ), I want
>> that started very seldom. But I do want the package installed so that when I
>> need it, it is there. Having it autostart as part of being installed is
>> breaking KISS and in some way unix philosophy: I asked for something to be
>> installed, not installed and autostarted.
> 
> That's cool. We can disagree on that. But the fact that you have to
> edit a file to enable things and hope you get the right start entry in
> /etc/rc.conf or /usr/local/etc/rc.conf, or wherever you put it is, is
> a pain.

In the context of the email thread, no one in their sane mind will configure 
Amazon/Heroku/etc. VMs manually.  They will use ansible/puppet/chef/etc. to 
install packages and to start services after they are installed and configured. 
 

I honestly don't see what the big deal is.  Most of the time you will need to 
configure your apache server before you can start it.  

--
Rui Paulo



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

[QAT] 362110: 4x leftovers

2014-07-18 Thread Ports-QAT 
- Update to latest upstream release 1.7.1
- Assign maintainership to Timothy Beyer 
  (previously ports@)
- General cleanup
- Add LICENSE
- Remove twelf from LEGAL (port is now BSD2CLAUSE licensed)

PR: 191758
Submitted by:   Timothy Beyer 
Approved by:mentors (implicit)
-

  Build ID:  20140716203801-993
  Job owner: ri...@freebsd.org
  Buildtime: 2 days
  Enddate:   Sat, 19 Jul 2014 03:08:37 GMT

  Revision:  362110
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=362110

-

Port:lang/twelf 1.7.1

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~ri...@freebsd.org/20140716203801-993-379310/twelf-1.7.1.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~ri...@freebsd.org/20140716203801-993-379311/twelf-1.7.1.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~ri...@freebsd.org/20140716203801-993-379312/twelf-1.7.1.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~ri...@freebsd.org/20140716203801-993-379313/twelf-1.7.1.log


--
Buildarchive URL: 
redports 
___
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"

[QAT] 362114: 4x leftovers

2014-07-18 Thread Ports-QAT 
Add a build dependency on intltool
Use options helpers
Fix building when no shared readline is in base
-

  Build ID:  20140716220800-17915
  Job owner: b...@freebsd.org
  Buildtime: 2 days
  Enddate:   Sat, 19 Jul 2014 03:24:25 GMT

  Revision:  362114
  Repository:
https://svnweb.freebsd.org/ports?view=revision&revision=362114

-

Port:security/gnomint 1.2.1_4

  Buildgroup: 8.4-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~b...@freebsd.org/20140716220800-17915-379326/gnomint-1.2.1_4.log

  Buildgroup: 8.4-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~b...@freebsd.org/20140716220800-17915-379327/gnomint-1.2.1_4.log

  Buildgroup: 9.2-QAT/amd64
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~b...@freebsd.org/20140716220800-17915-379328/gnomint-1.2.1_4.log

  Buildgroup: 9.2-QAT/i386
  Buildstatus:   LEFTOVERS
  Log: 
https://qat.redports.org//~b...@freebsd.org/20140716220800-17915-379329/gnomint-1.2.1_4.log


--
Buildarchive URL: 
redports 
___
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"