On Sun, Oct 13, 2013 at 01:36:45PM +0100, Chris Rees wrote:
> It appears that really weird SRCBASE assumptions are made throughout the
> code. I'll have to put a temporary hack in to just make SRCBASE appear
> inside the chroot whatever it's set to. Setting and unsetting SRCBASE just
> breaks dif
Hi,
I just faced the same problem.
On Thu, 06 Feb 2014 10:27:12 +0100
Rainer Hurling wrote:
>
>
> Am 06.02.2014 08:52 (UTC+1) schrieb Baptiste Daroussin:
> > On Thu, Feb 06, 2014 at 07:03:22AM +0100, Rainer Hurling wrote:
> >> Am 05.02.2014 22:20 (UTC+1) schrieb Baptiste Daroussin:
> >>> On W
> I'll see what I can find out. According to the (generally
> lua-knowledgable) prosody folks these libraries might even be merged in the
> future..
> For now I'll see if I can use the 0.9.1 patch (and bump it maybe?) so that
> I can prosody as my test application.
>
Sorry for replying to myself.
On 06/02/2014 12:45, Matthias Apitz wrote:
> Since many years I have always compiled "my" (i.e. the ports I need)
> from CVS or now SVN ports tree on some fast baquery maschine. After
> compiling I just did something like:
>
> # mkdir PKG
> # cd PKG
> # pkg_create -Rnb `cd /var/db/pkg ; ls -C1`
>
On 2014-02-03 08:32, Dewayne Geraghty wrote:
>
> On 2/02/2014 9:51 PM, olli hauer wrote:
>> On 2014-02-02 10:11, Dewayne Geraghty wrote:
>>> I filed a PR against textproc/htdig which should really be against the
>>> ports systems.
>>>
>>> Would someone be kind enough to advise the current method t
On Thu, Feb 6, 2014 at 9:05 PM, David Thiel
wrote:
> On 02/06, Benjamin Podszun wrote:
> > Maybe I can help with that - since I plan to migrate/relocate and
> > that's a core part of what I need here (which is why I'm diving into
> > ports about 30min after my first FreeBSD installation in years)
W dniu 2014-02-06 14:04, John Marino pisze:
> On 2/6/2014 13:58, Rick Miller wrote:
>> On Thu, Feb 6, 2014 at 7:23 AM, Daniel Nebdal wrote:
>>> I suspect he meant "a certain version, and *not* newer" - sometimes
>>> you might want to hold back a package.
>> Correct. My wish is the functional
On 02/06, Benjamin Podszun wrote:
> Maybe I can help with that - since I plan to migrate/relocate and
> that's a core part of what I need here (which is why I'm diving into
> ports about 30min after my first FreeBSD installation in years). So -
> one tester, ready to help out. ;-)
Thanks!
> Luaso
On 2/6/2014 17:13, Randy Pratt wrote:
> My experience with mixing ports and packages dates back to 2.2.5 and
> the disasters it created. Most of the problems were created by the
> ports tree and package builds not being syncronized. I switched to
> ports exclusively and have not had those problem
On Thu, Feb 6, 2014 at 7:55 PM, David Thiel wrote:
> On 02/06, Benjamin Podszun wrote:
> > > If you can try to coordinate with the luasec and luasocket maintainers
> ?
> >
> > Actually I think that's a non-issue (now). The comment from lx/the
> > maintainer of prosody claims that s2s is broken (n
On 2014-02-06 19:17, Michel Talon wrote:
>
> Le 6 févr. 2014 à 13:27, Julian H. Stacey a écrit :
>
>>>
>>> you =
>>> have to spend a couple of minutes
>>> learning the basic SQL queries, which is no more difficult that learning =
>>> obtuse find and grep options.
>>
>> Package addicts were so myo
On 02/06, Benjamin Podszun wrote:
> > If you can try to coordinate with the luasec and luasocket maintainers ?
>
> Actually I think that's a non-issue (now). The comment from lx/the
> maintainer of prosody claims that s2s is broken (no idea, haven't tried the
> patch just yet) and wonders if we'd
On 2014-02-06 13:45, Matthias Apitz wrote:
> El día Thursday, February 06, 2014 a las 01:27:50PM +0100, Julian H. Stacey
> escribió:
>
>> Michel Talon wrote:
>>
>>> The old package system was total =
>>> crap,
>>
>> local.sqlite is also crap, breaks decades of accessibility by find & grep
>> & ot
Le 6 févr. 2014 à 13:27, Julian H. Stacey a écrit :
>>
>> you =
>> have to spend a couple of minutes
>> learning the basic SQL queries, which is no more difficult that learning =
>> obtuse find and grep options.
>
> Package addicts were so myopic they ignored some people won't even
> use packag
El día Thursday, February 06, 2014 a las 03:55:57PM +0100, Christopher J. Ruwe
escribió:
> > > I think anybody who compiles from ports should _really_ use
> > > poudriere. I even think it should be strongly suggested in the
> > > handbook. (I'd be willing to write that up for that matter.)
> >
>
> https://plus.google.com/110946378055202199166/posts/8iTsSCatk4x
>
> The process has been started :
> http://forums.freebsd.org/viewtopic.php?f=39&t=44691
>
> Dependencies needed- referenced in "howto" and webrtc dependencies:
> libbrlapi from brltty.
>
>
> Benefits: Native client and sever si
On Thu, Feb 6, 2014 at 8:13 AM, Randy Pratt wrote:
> On Wed, 5 Feb 2014 23:26:18 -0800
> Kevin Oberman wrote:
>
> > On Wed, Feb 5, 2014 at 10:45 PM, Matthew Seaman <
> > m.sea...@infracaninophile.co.uk> wrote:
> >
> > > On 05/02/2014 23:57, Kevin Oberman wrote:
>
> > One BIG one that I know is
Stagify.
-
Build ID: 20140206155000-62431
Job owner: k...@freebsd.org
Buildtime: 38 minutes
Enddate: Thu, 06 Feb 2014 16:27:48 GMT
Revision: r343109
Repository:
http
05/02/14 18:41(e)an, Kevin Oberman(e)k idatzi zuen:
> Let's see. The instructions said to notify tms...@freebsd.org. I don't see
> any indication that you did so. They also say to attach the config.log
> file. I see no attached file.
>
> While it is possible that someone other than the maintaine
On Wed, 5 Feb 2014 23:26:18 -0800
Kevin Oberman wrote:
> On Wed, Feb 5, 2014 at 10:45 PM, Matthew Seaman <
> m.sea...@infracaninophile.co.uk> wrote:
>
> > On 05/02/2014 23:57, Kevin Oberman wrote:
> > > 1. The ports/packages system is not total crap. In fact, at the time jkh
> > > started it, it
Hi!
> > > Starting from 20.08.2013 prosody is on 0.9, 0.9.2 was released in
> > > January 2014.
> >
> > Have a look at
> >
> > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/182075
> >
> > there is an update to 0.9.1 as a patch and one open question
> > someone has to solve.
> Thanks for the li
Hi.
On Thu, Feb 6, 2014 at 4:06 PM, Kurt Jaeger wrote:
> Hi!
>
> > Starting from 20.08.2013 prosody is on 0.9, 0.9.2 was released in
> > January 2014.
>
> Have a look at
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/182075
>
> there is an update to 0.9.1 as a patch and one open question
>
Hi!
> Starting from 20.08.2013 prosody is on 0.9, 0.9.2 was released in
> January 2014.
Have a look at
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/182075
there is an update to 0.9.1 as a patch and one open question
someone has to solve.
> Is there any chance to see an update to this port?
On Thu, 6 Feb 2014 15:49:24 +0100
Matthias Apitz wrote:
> El día Thursday, February 06, 2014 a las 02:36:30PM +0100,
> Christopher J. Ruwe escribió:
>
> > On Wed, 5 Feb 2014 23:26:18 -0800
> > Kevin Oberman wrote:
> >
> > > If you use poudriere, you can roll your own packages with custom
> > >
On Thu, February 6, 2014 4:27 am, Julian H. Stacey wrote:
> Michel Talon wrote:
>
>
>
>>> ports/ is not just for package addicts. I never install packages, but
>>> only build & install from ports/. sqlite junk obstructs /var/db/pkg
>>> being accessed by find & grep to debug breaking ports =
>> b
El día Thursday, February 06, 2014 a las 02:36:30PM +0100, Christopher J. Ruwe
escribió:
> On Wed, 5 Feb 2014 23:26:18 -0800
> Kevin Oberman wrote:
>
> > If you use poudriere, you can roll your own packages with custom
> > options and maintain things pretty reasonably, but for a single
> > syst
Hey there.
Totally new to FreeBSD here, trying to migrate a piece of my
infrastructure from .. Linux.
One thing I'm relying on is prosody, you seem to maintain that port.
0.8.2 was released around the 20.06.2011.
Starting from 20.08.2013 prosody is on 0.9, 0.9.2 was released in
January 2014.
Is
On 2/6/14, 9:36 AM, N.J. Mann wrote:
In message <52f39326.2040...@marino.st>,
John Marino (freebsd.cont...@marino.st) wrote:
On 2/6/2014 14:31, N.J. Mann wrote:
You are asking for an infrastructure
change.
No I am not. I _am_ asking that something which used to be supported
(and wa
In message <52f39326.2040...@marino.st>,
John Marino (freebsd.cont...@marino.st) wrote:
> On 2/6/2014 14:31, N.J. Mann wrote:
>
> You are asking for an infrastructure
> change.
No I am not. I _am_ asking that something which used to be supported
(and was documented), that has silently be
Am 2014-02-06 14:05, schrieb Daniel Nebdal:
On Thu, Feb 6, 2014 at 1:45 PM, Matthias Apitz
wrote:
El día Thursday, February 06, 2014 a las 01:27:50PM +0100, Julian H.
Stacey escribió:
Michel Talon wrote:
> The old package system was total =
> crap,
local.sqlite is also crap, breaks decades
- Stage support
-
Build ID: 20140206122802-62035
Job owner: m...@freebsd.org
Buildtime: 94 minutes
Enddate: Thu, 06 Feb 2014 14:01:48 GMT
Revision: r343053
Repository:
On 2/6/2014 14:31, N.J. Mann wrote:
>> I don't believe it was ever a user variable.
> It was and still is for the base system - this machine was updated to
> 8-STABLE r261161 ten days ago and all base manual pages are
> uncompressed.
okay, that's right.
It's a case where ports honored a base varia
In message <52f388ee.30...@marino.st>,
John Marino (freebsd.cont...@marino.st) wrote:
> On 2/6/2014 13:54, N.J. Mann wrote:
> > For many years I have set NO_MANCOMPRESS (and before that NOMANCOMPRESS)
> > in /etc/make.conf on all my machines. In the last few weeks I have
> > noticed that t
On Wed, 5 Feb 2014 23:26:18 -0800
Kevin Oberman wrote:
> If you use poudriere, you can roll your own packages with custom
> options and maintain things pretty reasonably, but for a single
> system (or two), this is a bit of overkill. As things stand, this is
> a real pain to use customized ports
On 2/6/2014 13:54, N.J. Mann wrote:
> For many years I have set NO_MANCOMPRESS (and before that NOMANCOMPRESS)
> in /etc/make.conf on all my machines. In the last few weeks I have
> noticed that this setting is being ignored by port updates. Has this
> setting been silently depreciated?
>
You h
On Thu, Feb 6, 2014 at 1:45 PM, Matthias Apitz wrote:
> El día Thursday, February 06, 2014 a las 01:27:50PM +0100, Julian H. Stacey
> escribió:
>
>> Michel Talon wrote:
>>
>> > The old package system was total =
>> > crap,
>>
>> local.sqlite is also crap, breaks decades of accessibility by find &
On 2/6/2014 13:58, Rick Miller wrote:
> On Thu, Feb 6, 2014 at 7:23 AM, Daniel Nebdal wrote:
>
>> I suspect he meant "a certain version, and *not* newer" - sometimes
>> you might want to hold back a package.
>>
> Correct. My wish is the functionality be extended further to mean "a
> certain ver
Hi,
For many years I have set NO_MANCOMPRESS (and before that NOMANCOMPRESS)
in /etc/make.conf on all my machines. In the last few weeks I have
noticed that this setting is being ignored by port updates. Has this
setting been silently depreciated?
Cheers,
Nick.
--
___
On 2/6/2014 13:27, Julian H. Stacey wrote:
> Michel Talon wrote:
>> charset=us-ascii
>
> Junk mail format, not impressed. Use Ascii
This is petty.
>> i can only conclude, like
>> Matthew that you are being absurd.
> Personal inuendo does not impress.
While you may take this as an unnecess
On Thu, Feb 6, 2014 at 7:23 AM, Daniel Nebdal wrote:
> On Thu, Feb 6, 2014 at 12:41 PM, Rick Miller
> wrote:
> > On Thu, Feb 6, 2014 at 2:59 AM, Big Lebowski
> wrote:
> >
> >> On Thu, Feb 6, 2014 at 7:45 AM, Matthew Seaman <
> >> m.sea...@infracaninophile.co.uk> wrote:
> >>
> >> >
> >> > I'd be
El día Thursday, February 06, 2014 a las 01:27:50PM +0100, Julian H. Stacey
escribió:
> Michel Talon wrote:
>
> > The old package system was total =
> > crap,
>
> local.sqlite is also crap, breaks decades of accessibility by find & grep
> & other text pipe / search tools.
Since many years I ha
Michel Talon wrote:
>
> --Apple-Mail=_102D913B-49CA-4129-972A-758AABCAA293
> Content-Type: multipart/alternative;
> boundary="Apple-Mail=_16E0BC5A-FE3D-444D-8437-47827626590A"
>
>
> --Apple-Mail=_16E0BC5A-FE3D-444D-8437-47827626590A
> Content-Transfer-Encoding: quoted-printable
> Content-T
On Thu, Feb 6, 2014 at 12:41 PM, Rick Miller wrote:
> On Thu, Feb 6, 2014 at 2:59 AM, Big Lebowski wrote:
>
>> On Thu, Feb 6, 2014 at 7:45 AM, Matthew Seaman <
>> m.sea...@infracaninophile.co.uk> wrote:
>>
>> >
>> > I'd be interested to hear what features you think are missing. We will
>> > impl
On Thu, Feb 6, 2014 at 2:59 AM, Big Lebowski wrote:
> On Thu, Feb 6, 2014 at 7:45 AM, Matthew Seaman <
> m.sea...@infracaninophile.co.uk> wrote:
>
> >
> > I'd be interested to hear what features you think are missing. We will
> > implement anything (eventually...) that there is demand for and th
Am 06.02.2014 08:23 (UTC+1) schrieb Dimitry Andric:
> On 06 Feb 2014, at 07:48, Rainer Hurling wrote:
> ...
>> I just recognized, that in my CURRENT boxes in base their are two
>> versions of libc++:
>>
>> #ll /usr/lib/libc++.so*
>> -r--r--r-- 1 root wheel -134 3 Aug 22:33:00 2013 /usr/lib
Am 06.02.2014 08:52 (UTC+1) schrieb Baptiste Daroussin:
> On Thu, Feb 06, 2014 at 07:03:22AM +0100, Rainer Hurling wrote:
>> Am 05.02.2014 22:20 (UTC+1) schrieb Baptiste Daroussin:
>>> On Wed, Feb 05, 2014 at 09:19:51PM +0100, Matthias Andree wrote:
Am 05.02.2014 21:08, schrieb Dimitry Andri
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
On Thu, Feb 6, 2014 at 7:45 AM, Matthew Seaman <
m.sea...@infracaninophile.co.uk> wrote:
> On 05/02/2014 23:57, Kevin Oberman wrote:
> > 1. The ports/packages system is not total crap. In fact, at the time jkh
> > started it, it was far superior to any tool available.
>
> When I first encountered
48 matches
Mail list logo
