> On 09/30/13 07:15, Mathew Seaman wrote:
On 09/28/13 10:52, Gary Aitken wrote:
After switching to pkgng, I
noticed that my daily run output constantly complains about the
installed packages being corrupt, e.g.: "pkg_info: the package
info for package 'asciidoc-8.6.8_1' is
On Sun, Sep 29, 2013, at 23:09, Gary Aitken wrote:
>
> Some of the packages reported as corrupt were installed *after* the
> conversion to pkgng, so why is pkg_info even noticing them?
>
The only way this is possible is if they are in the old package format.
Did you happen to convert your packages
On 30/09/2013 06:09, Gary Aitken wrote:
>>> On 09/28/13 10:52, Gary Aitken wrote:
>>> After switching to pkgng, I noticed that my daily run output constantly
>>> complains about the installed packages being corrupt, e.g.:
>>> "pkg_info: the package info for package 'asciidoc-8.6.8_1' is corrupt"
>>On 09/28/13 10:52, Gary Aitken wrote:
>> After switching to pkgng, I noticed that my daily run output constantly
>> complains about the installed packages being corrupt, e.g.:
>> "pkg_info: the package info for package 'asciidoc-8.6.8_1' is corrupt"
>>
>> The problem is with
>> etc/periodic/
>>On 09/28/13 10:52, Gary Aitken wrote:
>> After switching to pkgng, I noticed that my daily run output constantly
>> complains about the installed packages being corrupt, e.g.:
>> "pkg_info: the package info for package 'asciidoc-8.6.8_1' is corrupt"
>>
>> The problem is with
>> etc/periodic/
Run pkg_info. If there is anything listed you have not fully converted
to pkgng and have some old broken/corrupt packages. You'll want to clean
this up.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-quest
After switching to pkgng, I noticed that my daily run output constantly
complains about the installed packages being corrupt, e.g.:
"pkg_info: the package info for package 'asciidoc-8.6.8_1' is corrupt"
The problem is with
etc/periodic/daily/490.status-pkg-changes
which is still using "pkg_inf