Hi everyone,
I have created a new article on the FreeBSD wiki which explains how to use
PkgBase for those that want to do some testing.
https://wiki.freebsd.org/PkgBase
The contents is based on the initial CFT email from Glen Barber to
freebsd-pkgbase mailing list on 2016-03-02:
https://lists.fre
Hi guys,
I am testing PkgBase and it is working very well - I really like it.
One minor problem I have noticed is that each time I do a "pkg upgrade -r
FreeBSD-base" it is overwriting /etc/pkg/FreeBSD.conf which I have edited
to disable the default repository. My expectation is that configuration
On Tuesday, 26 April 2016, Garrett Wollman wrote:
> < > said:
>
> > One minor problem I have noticed is that each time I do a "pkg upgrade -r
> > FreeBSD-base" it is overwriting /etc/pkg/FreeBSD.conf which I have edited
> > to disable the default repository. My expectation is that configuration
>
Hi everyone,
The commit in r299088 changes the behaviour for building multiple kernels
when the KERNCONF value contains multiple (space-separated) kernel conf
names.
https://svnweb.freebsd.org/base?view=revision&revision=299088
When PkgBase was announced by Glen Barber in March, note 4 of his ema
On Saturday, 7 May 2016, Glen Barber wrote:
> With 'installkernel', the first kernel listed in KERNCONF is installed
> as the default (/boot/kernel), and subsequent kernels are installed with
> the kernel name included in the path (/boot/kernel.${INSTKERNNAME}). In
> both cases (source-based upg
On 7 May 2016 at 09:41, Glen Barber wrote:
> I think this raises a larger question - did "something" change that
> otherwise violates POLA? The commit recently was intended to revert
> a POLA violation, so maybe I am not entirely clear on what branch this
> affects.
>
> Are we talking about head
On 7 May 2016 at 09:48, Ngie Cooper (yaneurabeya)
wrote:
> glebius changed the defaults to fix POLA, but the naming per the behavior
> is confusing. Right now the behavior between ^/head and ^/stable/10
> before/now match -- I just had to wrap my mind around the default being the
> affirmative of
On Saturday, 7 May 2016, David Wolfskill wrote:
>
> > If you list 2 kernels in the KERNCONF variable, why is it astonishing
> that
> > 2 kernels get installed? Even if the old behaviour was to only install 1
> > kernel, if you are listing 2 kernels in KERNCONF presumably that is
> because
> > you
Hi everyone,
I just re-built my FreeBSD 11 base packages, and it seems that as of the
FreeBSD 11 code slush in r300813 the packages now have version 11.0 instead
of the datestamp. This is obviously wrong, and if anything maybe they
should have 11.0-alpha1.
https://svnweb.freebsd.org/base?view=revi
Hi everyone,
I have just completed a packaged base upgrade, and for some reason the
/etc/rc.d/zfs and /etc/rc.d/zvol scripts are no longer in the
FreeBSD-runtime package.
Any ideas what the cause is for this?
Regards,
Ben
--
From: Benjamin Woods
woods...@gmail.com
__
On 27 May 2016 at 23:00, Glen Barber wrote:
> On Fri, May 27, 2016 at 10:54:12PM +0200, Ben Woods wrote:
> > Hi everyone,
> >
> > I have just completed a packaged base upgrade, and for some reason the
> > /etc/rc.d/zfs and /etc/rc.d/zvol scripts are no longer in the
On Saturday, 28 May 2016, Ben Woods wrote:
> On 27 May 2016 at 23:00, Glen Barber > wrote:
>
>> On Fri, May 27, 2016 at 10:54:12PM +0200, Ben Woods wrote:
>> > Hi everyone,
>> >
>> > I have just completed a packaged base upgrade, and for some reason
May 2016 at 19:57, Glen Barber wrote:
> On Sun, May 29, 2016 at 11:00:23AM +0200, Ben Woods wrote:
> > On Saturday, 28 May 2016, Ben Woods wrote:
> >
> > > On 27 May 2016 at 23:00, Glen Barber > > > wrote:
> > >
> > >> On Fri, May 27, 2016
On Monday, 30 May 2016, Glen Barber wrote:
>
> In the meantime, would you mind adding this particular issue (not the
> FreeBSD-zfs package, but the underlying problem) to the PkgBase wiki
> page?
>
Done.
Thanks,
Ben
--
--
From: Benjamin Woods
woods...@gmail.com
__
On 14 June 2016 at 09:11, René Ladan wrote:
> Hi,
>
> I updated my pkgbase installation (11.0-amd64 from a few weeks ago) to
> 11.0-ALPHA3. Building and installing went fine but it turns out that
> libpam.so* is lost in the update (both the symlink and the actual so,
> currently so.6) :
>
> # pkg
On Tuesday, 14 June 2016, Pavel Timofeev wrote:
>
> 14 июня 2016 г. 10:37 пользователь "Ben Woods" > написал:
> >
> > On 14 June 2016 at 09:11, René Ladan > wrote:
> >
> > > Hi,
> > >
> > > I updated my pkgbase installation (
Hi everyone,
Just a quick note to say that when trying to upgrade from 11-current to
12-current I got the following error:
# pkg upgrade -r FreeBSD-base
Updating FreeBSD-base repository catalogue...
Fetching meta.txz: 100%268 B 0.3kB/s00:01
Fetching packagesite.txz: 100% 52 KiB 52.9kB
Hi everyone,
I have noticed a number of files which do not seem to be part of the base
packages, and as such are not being updated on my system which is using
PkgBase. I realise the /etc config files are not included in base packages
yet, so I have excluded /etc from my investigation.
The files o
On Wednesday, 27 July 2016, Matthew Seaman wrote:
>
> Interesting. I've just seen exactly the same thing when trying to
> update my CURRENT VM. It's the transition from FreeBSD:11:amd64 to
> FreeBSD:12:amd64 which seems to be the root cause.
>
> The old 'freebsd:12:x86:64' ABI style is something
On Wednesday, 27 July 2016, Matthew Seaman wrote:
> Hmmm... where essentially the command you propose is:
>
> # env ABI=freebsd:12:x86:64 pkg upgrade -r FreeBSD-base
>
> Unfortunately this doesn't work:
>
> codling:/home/matthew:# env ABI=freebsd:12:x86:64 pkg upgrade -r
> FreeBSD-base
> pkg: War
On 11 July 2016 at 18:40, Ben Woods wrote:
> Hi everyone,
>
> I have noticed a number of files which do not seem to be part of the base
> packages, and as such are not being updated on my system which is using
> PkgBase. I realise the /etc config files are not included in base pac
On 25 January 2017 at 20:33, Joe Maloney via freebsd-pkgbase <
freebsd-pkgbase@freebsd.org> wrote:
> Hi,
> it looks like /usr/share/examples/etc/make.conf is being added to
> runtime.plist, and examples.plist. This causes installing, or upgrading
> freebsd-examples on it's own to prompt the user
On Thu, 10 Aug 2017 at 11:35 pm, Matthew Seaman wrote:
> On 10/08/2017 16:21, Glen Barber wrote:
> >> * Since we have no mechanism of properly merging changes to /etc
> >> we simply copy files as needed with pc-updatemanager, and it is
> >> difficult to maintain what should be updated, merged, or
On 3 September 2018 at 00:04, Brad Davis wrote:
> On Sun, Sep 2, 2018, at 4:46 AM, henry.v...@gmail.com wrote:
> > Hello,
> >
> > after successful building world and kernel(s) 'make packages' fails with
> > te following now:
> >
> > --- C U T ---
> >
> > ===> Creating FreeBSD-runtime-12.0.s201809
On 9 September 2018 at 03:29, Brad Davis wrote:
> On Sat, Sep 8, 2018, at 12:56 PM, Brad Davis wrote:
> > On Fri, Sep 7, 2018, at 11:17 PM, Ben Woods wrote:
> > > On 3 September 2018 at 00:04, Brad Davis wrote:
> > >> On Sun, Sep 2, 2018, at 4:46 AM, henry.v...@gm
Hi everyone,
Recently the default behaviour of pkg (or pkgbase?) was changed to install
any new files with a .pkgnew suffix.
My understand is that this was introduced to ensure pkg does not overwrite
any existing files that were not previously managed by pkg.
However, the current behaviour is th
).
Regards,
Ben Woods
woods...@freebsd.org
--
--
From: Benjamin Woods
woods...@gmail.com
___
freebsd-pkgbase@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-pkgbase
To unsubscribe, send any mail to "freebsd-pkgbase-uns
On Mon, 2 Mar 2020 at 23:04, Glen Barber wrote:
> On Sat, Feb 29, 2020 at 09:44:22AM +0800, Ben Woods wrote:
> > Just wanted to ask if there is a pkgbase repo for 13-CURRENT snapshots
> yet?
>
> There is not yet.
>
> Glen
>
Hi Glen,
Thanks for clarifying.
Out of cur
28 matches
Mail list logo
