Miroslav Lachman wrote on 12/20/2015 09:30:
olli hauer wrote on 12/19/2015 20:48:
On 2015-12-19 17:54, Miroslav Lachman wrote:
David Wolfskill wrote on 12/19/2015 14:46:
On Sat, Dec 19, 2015 at 02:26:47PM +0100, Miroslav Lachman wrote:
...
pkg update and pkg upgrade works fine for me too, bu
olli hauer wrote on 12/19/2015 20:48:
On 2015-12-19 17:54, Miroslav Lachman wrote:
David Wolfskill wrote on 12/19/2015 14:46:
On Sat, Dec 19, 2015 at 02:26:47PM +0100, Miroslav Lachman wrote:
...
pkg update and pkg upgrade works fine for me too, but pkg updating not. pkg
updating is intended
On 2015-12-19 17:54, Miroslav Lachman wrote:
> David Wolfskill wrote on 12/19/2015 14:46:
>> On Sat, Dec 19, 2015 at 02:26:47PM +0100, Miroslav Lachman wrote:
...
> pkg update and pkg upgrade works fine for me too, but pkg updating not. pkg
> updating is intended to read /usr/ports/UPDATING file a
David Wolfskill wrote on 12/19/2015 14:46:
On Sat, Dec 19, 2015 at 02:26:47PM +0100, Miroslav Lachman wrote:
Hi,
I am using own poudriere repo to build needed packages for our server. I
was used to `pkg_updating` or `pkg updating` in the past (when I was
compiling ports on each server).
I don't
On Sat, Dec 19, 2015 at 02:26:47PM +0100, Miroslav Lachman wrote:
> Hi,
> I am using own poudriere repo to build needed packages for our server. I
> was used to `pkg_updating` or `pkg updating` in the past (when I was
> compiling ports on each server).
> I don't have /usr/ports on server anymore.
Hi,
I am using own poudriere repo to build needed packages for our server. I
was used to `pkg_updating` or `pkg updating` in the past (when I was
compiling ports on each server).
I don't have /usr/ports on server anymore. So the `pkg updating` command
doesn't work. (There is no /usr/ports/UPDAT
