What you probably ran into is the common chicken and egg problem
where
if pkgng is upgraded ports, it blows up when it tries to deinstall the
package, or similarly, when portmaster is upgraded, it doesn't halt the
upgrade and restart it properly.
It's most likely still a problem; I'm goi
On 11/4/2012 5:06 AM, Darrel wrote:
>
> On Sat, 3 Nov 2012, Garrett Cooper wrote:
>
>> On Sat, Nov 3, 2012 at 6:15 PM, Darrel wrote:
>>
>> ...
>>
>> Yes, the existing man 8 pkg does not seem to match all of the facts.
>>
>>
>> What you probably ran into is the common chicken and egg proble
On Sat, 3 Nov 2012, Garrett Cooper wrote:
On Sat, Nov 3, 2012 at 6:15 PM, Darrel wrote:
...
Yes, the existing man 8 pkg does not seem to match all of the facts.
What you probably ran into is the common chicken and egg problem where
if pkgng is upgraded ports, it blows up when it tries
On Sat, Nov 3, 2012 at 6:15 PM, Darrel wrote:
...
> Yes, the existing man 8 pkg does not seem to match all of the facts.
>
What you probably ran into is the common chicken and egg problem where
if pkgng is upgraded ports, it blows up when it tries to deinstall the
package, or similarly, wh
pkg_info: Don't use the pkg_ tools if you are using pkgng
pkg_info: the package info for package 'ca_root_nss-3.14' is corrupt
have you run ever run pkg2ng ?
Hi, Eitan.
It could be that I had a case of bad luck. About an hour before the
documentation was put into /usr/ports/UPDATING, I
Is it possible to regenerate the package database or somehow start over? I
am seeing errors like these:
pkg_info: Don't use the pkg_ tools if you are using pkgng
pkg_info: the package info for package 'ca_root_nss-3.14' is corrupt
have you run ever run pkg2ng ?
Hi, Eitan.
It could be that
On 3 November 2012 20:37, Darrel wrote:
>
>>> Is it possible to regenerate the package database or somehow start over?
>>> I
>>> am seeing errors like these:
>>>
>>> pkg_info: Don't use the pkg_ tools if you are using pkgng
>>> pkg_info: the package info for package 'ca_root_nss-3.14' is corrupt
>
On 3 November 2012 15:57, Darrel wrote:
> Hello,
>
> Is it possible to regenerate the package database or somehow start over? I
> am seeing errors like these:
>
> pkg_info: Don't use the pkg_ tools if you are using pkgng
> pkg_info: the package info for package 'ca_root_nss-3.14' is corrupt
have
Is it possible to regenerate the package database or somehow
start over? I am seeing errors like these:
pkg_info: Don't use the pkg_ tools if you are using pkgng
pkg_info: the package info for package 'ca_root_nss-3.14' is
corrupt
If you still have the binari
If i read it right you need pkg info not pkg_info.
So use the old commands without the underscore.
I see the errors when running portmaster. Apparently, my 9.1 machines
upgraded alright to pkgng and something went awry with my 10.0 machine.
If I run something like 'pkg info | grep pkgcon
On Sat, Nov 3, 2012 at 12:57 PM, Darrel wrote:
> Hello,
>
> Is it possible to regenerate the package database or somehow start over? I
> am seeing errors like these:
>
> pkg_info: Don't use the pkg_ tools if you are using pkgng
> pkg_info: the package info for package 'ca_root_nss-3.14' is corrup
Hello,
Is it possible to regenerate the package database or somehow start over?
I am seeing errors like these:
pkg_info: Don't use the pkg_ tools if you are using pkgng
pkg_info: the package info for package 'ca_root_nss-3.14' is corrupt
Darrel
___
12 matches
Mail list logo
