Solved [Solved] Using pkg (split from unstaged ports thread)

protocelt · Sep 15, 2014

Re: Using pkg (split from unstaged ports thread)

ghostcorps said:
Is there a dirty way to have portmaster ignore cvsup?

Code:

-x  avoid building or updating ports that match this pattern.  Can be
    specified more than once.  If a port is not already installed the
    exclude pattern will be run against the directory name from
    /usr/ports.

I think the better way however is to first delete both the cvsup and ezm3 installed packages with # pkg delete -f cvsup ezm3. portmaster should then continue correctly.

kpa · Sep 15, 2014

Re: Using pkg (split from unstaged ports thread)

protocelt said:
ghostcorps said:

Is there a dirty way to have portmaster ignore cvsup?

Click to expand...

From portmaster(8):

Code:

-x avoid building or updating ports that match this pattern. Can be specified more than once. If a port is not already installed the exclude pattern will be run against the directory name from /usr/ports.

I think the better way however is to first delete both the cvsup and ezm3 installed packages with # pkg delete -f cvsup ezm3. portmaster should then continue correctly.

Both ports are deleted so there's no way to get them back anyway. Deleting the packages should succeed with just # pkg delete -R cvsup ezm3 (do take note what the list of packages to be deleted contains before answering yes) that deletes all installed packages that depend on the listed packages. Using pkg delete -f should be avoided unless there's no other option.

protocelt · Sep 15, 2014

Re: Using pkg (split from unstaged ports thread)

kpa said:
Both ports are deleted so there's no way to get them back anyway. Deleting the packages should succeed with just # pkg delete -R cvsup ezm3 (do take note what the list of packages to be deleted contains before answering yes) that deletes all installed packages that depend on the listed packages. Using pkg delete -f should be avoided unless there's no other option.

Ugh. Thanks for the correction. Lack of sleep is showing...

ghostcorps · Sep 15, 2014

Re: Using pkg (split from unstaged ports thread)

Solved

After all the work we have done, something must have clicked:

I was now able to delete cvsup & ezm3 with a simple:

#pkg delete cvsup-without-gui-16.1h_7
#pkg delete ezm3-1.1_2

This was a great learning experience. It shows I really needed to get my head around pkg much sooner but I have learned a truck load.

Thanks everyone

I hope this helps someone in the future.

ghostcorps · Sep 15, 2014

Re: Using pkg (split from unstaged ports thread)

@ protocelt

I must have been doing that as you were typing the suggestion.

I think the full package name was needed because it was not listed in the new package database. I used the names from the old /var/db/pkg.

ghostcorps · Sep 18, 2014

Hi Guys,

I hope it is ok to reopen this thread, the problem is similar and follows on from the requirements for the ports-mgmt/pkg upgrade to 1.3.7.

After getting a better understanding of ports-mgmt/pkg from this discussion, I moved to updating the important server.

The upgrade went smoothly until I found that www/mod_php55 would not reinstall without also installing www/apache24, strange because pkg info -fd www/mod_php55 shows a dependency on www/apache22.

Code:

# uname -a
FreeBSD DOMAIN 10.0-RELEASE-p3 FreeBSD 10.0-RELEASE-p3 #0: Tue May 13 18:31:10 UTC 2014     root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64

I followed /usr/ports/UPDATING to stay with www/apache22 when www/apache24 became the default and have never had any trouble till now.

/etc/make.conf

Code:

WITH_PKGNG=yes
DEFAULT_VERSIONS+=apache=2.2

Seems normal?

Code:

# pkg -vv
Version                 : 1.3.7
PKG_DBDIR = "/var/db/pkg";
PKG_CACHEDIR = "/var/cache/pkg";
PORTSDIR = "/usr/ports";
INDEXDIR = "";
INDEXFILE = "INDEX-10";
HANDLE_RC_SCRIPTS = false;
ASSUME_ALWAYS_YES = false;
REPOS_DIR [
    "/etc/pkg/",
    "/usr/local/etc/pkg/repos/",
]
PLIST_KEYWORDS_DIR = "";
SYSLOG = true;
ABI = "freebsd:10:x86:64";
DEVELOPER_MODE = false;
VULNXML_SITE = "http://www.vuxml.org/freebsd/vuln.xml.bz2";
FETCH_RETRY = 3;
PKG_PLUGINS_DIR = "/usr/local/lib/pkg/";
PKG_ENABLE_PLUGINS = true;
PLUGINS [
]
DEBUG_SCRIPTS = false;
PLUGINS_CONF_DIR = "/usr/local/etc/pkg/";
PERMISSIVE = false;
REPO_AUTOUPDATE = true;
NAMESERVER = "";
EVENT_PIPE = "";
FETCH_TIMEOUT = 30;
UNSET_TIMESTAMP = false;
SSH_RESTRICT_DIR = "";
PKG_ENV {
}
DISABLE_MTREE = false;
PKG_SSH_ARGS = "";
DEBUG_LEVEL = 0;
ALIAS {
}
CUDF_SOLVER = "";
SAT_SOLVER = "";
RUN_SCRIPTS = true;
CASE_SENSITIVE_MATCH = false;
LOCK_WAIT = 1;
LOCK_RETRIES = 5;
SQLITE_PROFILE = false;
WORKERS_COUNT = 0;
READ_LOCK = false;


Repositories:
  FreeBSD: {
    url             : "pkg+http://pkg.FreeBSD.org/freebsd:10:x86:64/latest",
    enabled         : yes,
    mirror_type     : "SRV",
    signature_type  : "FINGERPRINTS",
    fingerprints    : "/usr/share/keys/pkg"
  }

This was looking good.

Code:

# # pkg update -f
Updating FreeBSD repository catalogue...
Fetching meta.txz: 100%   944 B   0.9k/s    00:01
Fetching digests.txz: 100%    2 MB   2.0M/s    00:01
Fetching packagesite.txz: 100%    5 MB   5.2M/s    00:01
Processing new repository entries: 100%
FreeBSD repository update completed. 23330 packages processed:
  0 updated, 0 removed and 23330 added.

Code:

 # pkg check -Ba
Checking all packages: 100%

Code:

# pkg upgrade
Updating FreeBSD repository catalogue...
FreeBSD repository is up-to-date.
All repositories are up-to-date.
Updating database digests format: 100%
Checking for upgrades (58 candidates): 100%
The following 3 packages will be affected (of 0 checked):

New packages to be INSTALLED:
        apache24: 2.4.10_1

Installed packages to be REINSTALLED:
        mod_php55-5.5.16 (options changed)
        php55-5.5.16 (options changed)

The process will require 22 MB more space.
6 MB to be downloaded.

Proceed with this action? [y/N]: N

Code:

# pkg audit
0 problem(s) in the installed packages found.

Initially, this was a much larger list but by manually using pkg upgrade on the other ports I was able to get the outstanding list down to www/mod_php55 and lang/php55

Manually reinstalling these with ports-mgmt/portmaster did not clear it, but I have been considering locking www/apache22 before running pkg upgrade again but I am not sure if this will cause any conflicts later on.

Do I just need to work around it till www/apache24 can be installed?

Thanks for reading.

SirDice · Sep 18, 2014

ghostcorps said:
I followed /usr/ports/UPDATING to stay with www/apache22 when www/apache24 became the default and have never had any trouble till now.

/etc/make.conf

Code:

WITH_PKGNG=yes DEFAULT_VERSIONS+=apache=2.2

Seems normal?

Yes, but those settings only have an effect when building from ports. Package dependencies are fixed and cannot be changed at this time. Packages are built using the default settings which means mod_php* now depends on apache24 instead of apache22.

ghostcorps · Sep 19, 2014

Re: [Reopened] Using pkg (split from unstaged ports thread)

Thanks SirDice,

I understand what you are saying. I will get to work on www/apache24. I seem to recall reading that FreeBSD 10 and www/apache24 don't play well together, is this true?

When I said, 'seems normal' I was referring to the output of pkg -vv, not that it makes a difference

SirDice · Sep 19, 2014

Re: [Reopened] Using pkg (split from unstaged ports thread)

ghostcorps said:
I seem to recall reading that FreeBSD 10 and www/apache24 don't play well together, is this true?

If this was the case it wouldn't be set as default.

ghostcorps · Sep 20, 2014

True,

It must have been an old thread.

Solved [Solved] Using pkg (split from unstaged ports thread)

protocelt

kpa

protocelt

ghostcorps

ghostcorps

ghostcorps

SirDice

Administrator

ghostcorps

SirDice

Administrator

ghostcorps