Re: poudriere and MAKEOBJDIRPREFIX

Am Fri, 11 Mar 2016 09:47:06 -0800 Bryan Drewery schrieb: > On 3/10/2016 5:37 AM, O. Hartmann wrote: > > env MAKEOBJDIRPREFIX=/some/place poudriere jail -c -j 10-stable-amd64 \ > > -a amd64 -v stable/10 -m src=/somesrc/srcplace/ > > > > In poudriere.conf I added > > > >

Re: print/cups overhaul (PR 207746) side-effects

Hello, Jim Ohlstein > On Mar 11, 2016, at 2:52 PM, Martin Waschbüsch wrote: > > Hi all, > > I just did a rebuild of packages for my webservers with poudriere. > What I noticed was that via the print/cups overhaul (see PR 207746), > quite a lot (>50) of additional

print/cups overhaul (PR 207746) side-effects

Hi all, I just did a rebuild of packages for my webservers with poudriere. What I noticed was that via the print/cups overhaul (see PR 207746), quite a lot (>50) of additional dependencies are added to the system, including lots of x11 related libs, avahi, dbus, cairo, opengl, etc. This stems

Re: Asterisk 2.x ???

On 03/11/16 19:52, pathiaki2 wrote: > Hi, > > Since Asterisk 1.8 is now deprecated, what are the port plans for > Asterisk 2.x ? > There will never be asterisk 2.0. Due to this, some years ago, the asterisk project decided to simply drop the "1.", skip the number 9, and have even versions be

Re: [CFT] net-im/ejabberd to 16.02

On Fri, 11 Mar 2016 19:00:54 +0100, Kurt Jaeger said: | Hi! || | https://people.freebsd.org/~ashish/diffs/ejabberd-16.02-1.diff || || Correct URL is: https://people.freebsd.org/~ashish/diffs/ejabberd-16.02-2.diff | The update hit the tree. Thanks for the persistence in

Asterisk 2.x ???

Hi, Since Asterisk 1.8 is now deprecated, what are the port plans for Asterisk 2.x ? Thank you, Paul Pathiakis ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to

Re: [CFT] net-im/ejabberd to 16.02

Hi! > | https://people.freebsd.org/~ashish/diffs/ejabberd-16.02-1.diff > > Correct URL is: https://people.freebsd.org/~ashish/diffs/ejabberd-16.02-2.diff The update hit the tree. Thanks for the persistence in providing this patch! -- p...@opsec.eu+49 171 3101372

Re: poudriere and MAKEOBJDIRPREFIX

On 3/10/2016 5:37 AM, O. Hartmann wrote: > env MAKEOBJDIRPREFIX=/some/place poudriere jail -c -j 10-stable-amd64 \ > -a amd64 -v stable/10 -m src=/somesrc/srcplace/ > > In poudriere.conf I added > > export MAKEOBJDIRPREFIX=$MAKEOBJDIRPREFIX > > as recommended in some posts I found googling for

Re: pkg: fetching binary packages to a local dumpdir for a different ABI

Mathieu Arnold wrote on 03/11/2016 18:26: +--On 11 mars 2016 13:04:11 +0100 Miroslav Lachman <000.f...@quip.cz> wrote: | Matthew Seaman wrote on 03/11/2016 12:15: |> On 03/11/16 10:00, Miroslav Lachman wrote: |>> O. Hartmann wrote on 03/11/2016 10:42: |>> |>> [...] |>> |>>> The ABI is also

Re: pkg: fetching binary packages to a local dumpdir for a different ABI

+--On 11 mars 2016 13:04:11 +0100 Miroslav Lachman <000.f...@quip.cz> wrote: | Matthew Seaman wrote on 03/11/2016 12:15: |> On 03/11/16 10:00, Miroslav Lachman wrote: |>> O. Hartmann wrote on 03/11/2016 10:42: |>> |>> [...] |>> |>>> The ABI is also unclear. Some documents say it is

Re: FreeBSD ports you maintain which are out of date

+--On 11 mars 2016 17:51:41 +0100 Martin Waschbüsch wrote: | |> Am 11.03.2016 um 13:41 schrieb Ryan Steinmetz : |> |> |> On (03/11/16 12:35), Raphael Kubo da Costa wrote: |>> Mathieu Arnold writes: |>>> Someone already put: |>>> |>>>

Re: pkg: fetching binary packages to a local dumpdir for a different ABI

Am Fri, 11 Mar 2016 11:00:28 +0100 Miroslav Lachman <000.f...@quip.cz> schrieb: > O. Hartmann wrote on 03/11/2016 10:42: > > [...] > > > The ABI is also unclear. Some documents say it is freebsd:10:x86:64 (which > > looks more the Intel/Linux dominated terminology) and also this one is > >

Re: FreeBSD ports you maintain which are out of date

> Am 11.03.2016 um 13:41 schrieb Ryan Steinmetz : > > > On (03/11/16 12:35), Raphael Kubo da Costa wrote: >> Mathieu Arnold writes: >>> Someone already put: >>> >>> PORTSCOUT= ignore >> >> I did that in r410199, and tried a different approach first in

Re: pkg: fetching binary packages to a local dumpdir for a different ABI

On 2016/03/11 12:04, Miroslav Lachman wrote: > Matthew Seaman wrote on 03/11/2016 12:15: >> On 03/11/16 10:00, Miroslav Lachman wrote: >>> O. Hartmann wrote on 03/11/2016 10:42: >>> >>> [...] >>> The ABI is also unclear. Some documents say it is freebsd:10:x86:64 (which looks more

(GSoC 2016) Parallel ports build and installation => paraports

Hi to all. Last year I overlooked the calendar, so am now proposing this project again. Would there be interest for it and mentor too? To cut it short, it works like this: http://starforce.biz/paraports.mp4 PS: It is video from last year. Now it works better and faster. Domagoj

Re: FreeBSD ports you maintain which are out of date

Ryan Steinmetz writes: > On (03/11/16 12:35), Raphael Kubo da Costa wrote: >>Mathieu Arnold writes: >>> Someone already put: >>> >>> PORTSCOUT= ignore >> >>I did that in r410199, and tried a different approach first in r410104. >>It's not clear to me why

Re: FreeBSD ports you maintain which are out of date

On (03/11/16 12:35), Raphael Kubo da Costa wrote: Mathieu Arnold writes: Someone already put: PORTSCOUT= ignore I did that in r410199, and tried a different approach first in r410104. It's not clear to me why these reports are still being sent. ignore: Set to 1 to

Re: pkg: fetching binary packages to a local dumpdir for a different ABI

Matthew Seaman wrote on 03/11/2016 12:15: On 03/11/16 10:00, Miroslav Lachman wrote: O. Hartmann wrote on 03/11/2016 10:42: [...] The ABI is also unclear. Some documents say it is freebsd:10:x86:64 (which looks more the Intel/Linux dominated terminology) and also this one is considered

Re: FreeBSD ports you maintain which are out of date

Mathieu Arnold writes: > +--On 9 mars 2016 07:16:14 -0500 Ryan Steinmetz wrote: > | > | On (03/09/16 13:11), Mathieu Arnold wrote: > |> Hi, > |> > |> This really is getting annoying. > |> > | > | You can control the behavior by setting portscout flags on

Re: pkg: fetching binary packages to a local dumpdir for a different ABI

On 03/11/16 09:42, O. Hartmann wrote: > The process will require 4 GiB more space. > 4 GiB to be downloaded. > Fetching pkg-1.6.4_1.txz: 100%3 MiB 562.3kB/s00:05 > pkg-static: cached package pkg-1.6.4_1: size mismatch, fetching from remote > Fetching pkg-1.6.4_1.txz: 100%3 MiB

Re: pkg: fetching binary packages to a local dumpdir for a different ABI

On 03/11/16 10:00, Miroslav Lachman wrote: > O. Hartmann wrote on 03/11/2016 10:42: > > [...] > >> The ABI is also unclear. Some documents say it is freebsd:10:x86:64 >> (which >> looks more the Intel/Linux dominated terminology) and also this one is >> considered correct: FreeBSD:10:amd64

Re: pkg: fetching binary packages to a local dumpdir for a different ABI

O. Hartmann wrote on 03/11/2016 10:42: [...] The ABI is also unclear. Some documents say it is freebsd:10:x86:64 (which looks more the Intel/Linux dominated terminology) and also this one is considered correct: FreeBSD:10:amd64 (looks more FreeBSD'ish). It is said that the variable ABI is

pkg: fetching binary packages to a local dumpdir for a different ABI

On CURRENT, I try to "silly fetch" a selection of binary packages for FreeBSD 10-STABLE from a regular user via this command sequence: env ABI=freebsd:10:x86:64 PKG_CACHEDIR=./tmp/packages/cache \ REPOS_DIR=./tmp/packages cat /usr/local/etc/poudriere.d/pkglist | \ xargs pkg fetch -y -U -d -o

FreeBSD ports you maintain which are out of date

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,

Re: lang/python27: Failed: stage

poudriere build fine for: 9.3 amd + i386 10.2 amd + i386 11-current r295432 amd + i386 Cheers jochen On 03/11/16 09:29, O. Hartmann wrote: > Try to build lang/python27 within poudriere. The base system is running recent > CURRENT, the jail used is a 10-STABLE, compiled locally on the CURRENT

lang/python27: Failed: stage

Try to build lang/python27 within poudriere. The base system is running recent CURRENT, the jail used is a 10-STABLE, compiled locally on the CURRENT box. While lang/python27 compiles fine using a head-jail built from the CURRENT sources, I receive a sticky and nasty error when trying to build the