Summary: | ports-mgmt/portupgrade: with portupgrade -P install of ports-mgmt/pkg fails | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | Fabian Wenk <fabian> |
Component: | Individual Port(s) | Assignee: | freebsd-ports-bugs (Nobody) <ports-bugs> |
Status: | Open --- | ||
Severity: | Affects Some People | CC: | bdrewery, fernape, grahamperrin, michael.osipov |
Priority: | --- | Flags: | fernape:
maintainer-feedback?
(bdrewery) |
Version: | Latest | ||
Hardware: | Any | ||
OS: | Any |
Description
Fabian Wenk
2023-03-12 14:55:45 UTC
While I don't know whether this is a genuine bug or not, but as mentioned in the other ticket I recommend doing this with poudriere, then you can upgrade with "pkg upgrade". Done. pkg and pkg-static both belong to the pkg package, so using either won't change anything if I am understanding this correctly. I remove pkg@ from cc as this has nothing to do with pkg itself. (In reply to Baptiste Daroussin from comment #2) Running on the build system (where the port is build from source) with: portupgrade -pa this gets logged into syslog: Sep 22 20:15:42 riddler pkg[59460]: webp-1.3.1_1 deinstalled Sep 22 20:15:44 riddler pkg-static[59708]: webp-1.3.2 installed And running on any of the other systems (where an available pre-built package is taken) with: portupgrade -kPa this gets logged into syslog: Sep 22 20:44:48 batman pkg[4699]: webp-1.3.1_1 deinstalled Sep 22 20:44:49 batman pkg[4728]: webp-1.3.2 installed Usually this does not make a difference, unless there is an update for ports-mgmt/pkg itself. On the build system it works just fine, but then fails on the other systems and leaves them in a broken state where ports-mgmt/pkg is removed. The only way out of this is with a local manual build like this: cd /usr/ports/ports-mgmt/pkg make install So my (slightly rewritten) question from the original report still stands: Why is 'portupgrade -P' using 'pkg' instead of 'pkg-static' when upgrading from a package instead of a locally done build? Some other thoughts, could it be that portupgrade is taking different steps / commands when run with -P during install from a local build or a package? So what I see in syslog with the 'pkg' and 'pkg-static' is just a coincident? |