Miroslav Lachman writes:
> [...]
> Any possibility that you have some kind of automatic snapshoting utility
> run from crontab recursively on filesystem where poudriere have builder
> jails mounted?
>
> I saw this error when I setup zfsnap in crontab with resursive snapshot
> of /vol0 (e
I have a FreeBSD 12.1p3 (just updated) root-on-zfs system that's
having trouble doing Poudriere builds.
It started off life as a FreeBSD 12.1 system and has been building
it's own set of packages using Poudriere successfully since its
inception.
I few updates ago I started seeing errors in the
Baptiste Daroussin writes:
>
> You should really have a look at overlays which are supported in
> poudriere-devel, it will allow you to get rid of portshaker with your use
> case:
>
> https://reviews.freebsd.org/rP510950
>
> in poudriere an overlay is just a "regular ports tree" appende
@lbutlr writes:
> [...]
> Not sure I quite get how the Webserver lets your other machines get
> the packages in such a way that they can be dropped in place, [...]
Nicely described in the DigitalOcean Tutorial[do]
But basically, you put your tree full of built packages somewhere
where the
Dan McGrath writes:
> [...] I am not sure about repo priorities, or how you would deal
> with conflicts with build options that pull in common ports. It is
> something I have been meaning to look into, sorry! Perhaps someone else
> here can give some advice?
>
One way to solve this is via "po
John Kennedy writes:
> On Sat, Feb 15, 2020 at 09:02:39PM -0700, @lbutlr wrote:
> > [...]
> > Am I writing a config file for this every port I want to build?
>
> Personally, I have a single, custom make.conf that I maintain and shove into
> /usr/local/etc/poudriere.d (default location I belie
@lbutlr writes:
> On 15 Feb 2020, at 21:43, Dan McGrath wrote:
> > You would run "poudriere bulk", then sit back sipping coffee while it
> > churns through all of the packages.
>
> Hang on a second, so the intended use for poudriere is to build ALL
> packages?
That's not a poudriere constra
@lbutlr writes:
> [...]
> Sorry for the rather basic questions.
>
I'm also a poudriere beginner and/but I found this DigitalOcean
tutorial very useful:
https://www.digitalocean.com/community/tutorials/how-to-set-up-a-poudriere-build-system-to-create-packages-for-your-freebsd-servers
g.
__
Mathieu Arnold writes:
> [...]
> Flavors have been documented from day one.
>
> https://www.freebsd.org/doc/en/books/porters-handbook/flavors.html
>
> (I kinda know because I wrote (most of) the flavors code, and I also
> write (most of) the documentation.)
But, and I think that this is whe
On Sep 25, 2019, at 3:49 PM, Polytropon wrote:
>
> On Wed, 25 Sep 2019 09:18:36 -0700, George Hartzell wrote:
>> I wasn't aware of PORTSDIR, I'm a long time ports user but this is my
>> first foray into not simply using the stock FreeBSD ports tree.
>
&
Romain Tartière writes:
> [...]
> Can you try setting PORTSDIR to your target ports tree, e.g.
>
> % sudo env PORTSDIR=/usr/local/poudriere/ports/default portshaker -M
Setting PORTSDIR fixes it for me (different directory, but it works).
> My guess is that since Mk/bsd.port.mk was not found
George Hartzell writes:
>
> I've been happily using portshaker to merge my "personal" ports tree
> [1] with the standard tree, then building things with poudriere. Up
> until today the things in my tree were additions.
>
> Today I tried rep
I've been happily using portshaker to merge my "personal" ports tree
[1] with the standard tree, then building things with poudriere. Up
until today the things in my tree were additions.
Today I tried replacing the standard copy of audio/logitechmusicserver
with a customized version that includ
George Hartzell writes:
> Brooks Davis writes:
> > On Sat, Jul 03, 2010 at 12:45:49PM -0700, George Hartzell wrote:
> > > Emanuel Haupt writes:
> > > > George Hartzell wrote:
> > > > > Emanuel Haupt writes:
> > > > &
Brooks Davis writes:
> On Sat, Jul 03, 2010 at 12:45:49PM -0700, George Hartzell wrote:
> > Emanuel Haupt writes:
> > > George Hartzell wrote:
> > > > Emanuel Haupt writes:
> > > > > Hi
> > > > >
> > > &
Emanuel Haupt writes:
> George Hartzell wrote:
> > Emanuel Haupt writes:
> > > Hi
> > >
> > > The current audio/squeezeboxserver port is still broken for me. I
> > > just built a package set with an up to date ports tree and
> > &
Emanuel Haupt writes:
> Hi
>
> The current audio/squeezeboxserver port is still broken for me. I just
> built a package set with an up to date ports tree and installed them in
> a vanilla jail to make sure that there is no previous cruft which could
> possibly be a problem.
>
> After inst
Mark writes:
> Hi,
> I've been using this port for some years to power my Squeezebox devices
> - thanks for keeping it up to date.
>
> However, the latest update has killed my installation totally - first it
> would not scan my music, and after upgrading perl & perl module ports I
> can
Coleman Kane writes:
> On Mon, 2008-06-16 at 18:41 +0200, jean-christophe wrote:
> > hello,
> >
> > i would like know if a new version of radeonhd port is prevu.
> > [...]
>
> Probably not until they release a new driver. However, I've just been
> following their git tree directly and tha
Michael Fuhr writes:
> [...]
> The "ident sameuser" method causes the backend to ask the OS what
> user is at the other end of the Unix socket. If the OS username
> matches the database username then the connection is authenticated;
> otherwise it's rejected. You can use pg_ident.conf to def
Michael Fuhr writes:
> On Mon, Jan 29, 2007 at 09:23:52AM -0500, Bill Moran wrote:
> > In response to George Hartzell <[EMAIL PROTECTED]>:
> > > I've "solved" the problem by creating a ~pgsql/.pgpass file with the
> > > pgsql user
Bill Moran writes:
> In response to George Hartzell <[EMAIL PROTECTED]>:
> >
> > I'm curious how other freebsd postgresql users handle databases with
> > passwords and running the 502.pgsql periodic script.
> >
> > I've "solved&q
I'm curious how other freebsd postgresql users handle databases with
passwords and running the 502.pgsql periodic script.
I've "solved" the problem by creating a ~pgsql/.pgpass file with the
pgsql users password.
Is there a better way?
g.
___
freebsd-
23 matches
Mail list logo
