portmaster creating corrupt legacy pkg db entries

[sysfu]

This happens with any application that is upgraded using portmaster. pkgng db entries are not corrupt.

Environment:
FreeNAS-9.2.1.3-RELEASE-x64 standard FreeBSD 9.2 x64 jail
portmaster-3.17.4

/etc/make.conf
WITH_PKGNG=yes
WITH_OPENSSL_PORT=yes
NO_WARNING_PKG_INSTALL_EOL=yes

Step to reproduce:

# pkg_info
pkg_info: no packages installed

# portmaster -r pkg-1.2.7
===>>> Working on:        pkg-1.2.7
===>>> Gathering distinfo list for installed ports
===>>> pkg-1.2.7 1/1
===>>> Currently installed version: pkg-1.2.7
<snip>
===>>> The following actions were performed:
        Upgrade of pkg-1.2.7 to pkg-1.2.7_2
===>>> Exiting

 # pkg_info
pkg_info: the package info for package 'pkg-1.2.7_2' is corrupt

[bdrewery]

It's not really corrupt. pkg_info is no longer valid to use after converting to pkgng. Use 'pkg info'.

It is known portmaster writes to the wrong place and causes these messages.

Sent from my iPhone

On Apr 3, 2014, at 17:59, Seth notifications@github.com wrote:

This happens with any application that is upgraded using portmaster. pkgng db entries are not corrupt.

Environment:
FreeNAS-9.2.1.3-RELEASE-x64 standard FreeBSD 9.2 x64 jail
portmaster-3.17.4

/etc/make.conf
WITH_PKGNG=yes
WITH_OPENSSL_PORT=yes
NO_WARNING_PKG_INSTALL_EOL=yes
Step to reproduce:

pkg_info

pkg_info: no packages installed

portmaster -r pkg-1.2.7

===>>> Working on: pkg-1.2.7
===>>> Gathering distinfo list for installed ports
===>>> pkg-1.2.7 1/1
===>>> Currently installed version: pkg-1.2.7

===>>> The following actions were performed:
Upgrade of pkg-1.2.7 to pkg-1.2.7_2
===>>> Exiting

pkg_info

pkg_info: the package info for package 'pkg-1.2.7_2' is corrupt
—
Reply to this email directly or view it on GitHub.

[sysfu]

Is there an existing portmaster github issue that addresses this problem? I would like to subscribe to notifications for it.

[bdrewery]

On Apr 3, 2014, at 20:01, Seth notifications@github.com wrote:

Is there an existing portmaster github issue that addresses this problem? I would like to subscribe to notifications for it.

Looks like this is it :)

Thought for sure there was one already. It's at least been known since pkgng was integrated. Workarounds were added to pkg_info on 10, but it was removed by release time. There is also some logic in pkg2ng to avoid the issue.