Date: Wed, 27 May 2026 02:22:16 +0100 From: Kaya Saman <kayasaman@optiplex-networks.com> To: questions@freebsd.org Subject: Re: Upgraded from 13.x release to 14.4 and now I can't use the ports tree? Message-ID: <1cc06f0d-d10c-44bc-90de-bf1e1c1a61ea@optiplex-networks.com> In-Reply-To: <CALvWPyawLXn6eawFjud953UCQvZHbkFZ9_EEeEeaazR9EsoujQ@mail.gmail.com> References: <27136c7e-8026-4e1e-9714-497a75c74ede@optiplex-networks.com> <SA1PR11MB881181F39DB1347A0DF364F9E60B2@SA1PR11MB8811.namprd11.prod.outlook.com> <CALvWPyawLXn6eawFjud953UCQvZHbkFZ9_EEeEeaazR9EsoujQ@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] Hi, On 5/26/26 9:23 PM, Maku Bex wrote: > You ran the commands under '/usr/ports' instead of > '/usr/ports/ports-mgmt/portmaster'. You need to `cd` to the port > name's folder then run the commands. In your case: > > # cd /usr/ports/ports-mgmt/portmaster > # make check-plist && make stage-qa > Sorry I think I just blindly followed instructions or misunderstood as I had been awake for a little too long. Some good news, after removing and re-fetching the ports tree, I was able to rebuild Portmaster through using the standard "make" command and portmaster itself. At the moment, I've just done a: portmaster -adyf --no-confirm hopefully if the @ports system has stabilized now it should be able to complete the build of Perl which it got stuck on. Currently it's on 9 out of 828 ports, so maybe in a few hours once it gets to say port 11 or something where Perl gets rebuilt I should know. The machine is only a quad core Xeon so this will take some time but hopefully now it will build? I'll keep everyone posted :-) Regards, Kaya > On Tue, May 26, 2026, 14:31 Edward Sanford Sutton, III > <mirror176@hotmail.com> wrote: > > On 5/25/26 22:43, Kaya Saman wrote: > > Hi, > > > > > > I've just gone through the upgrade procedure described here: > > > > > > https://docs.freebsd.org/en/books/handbook/cutting-edge/ > > > > > > and updated to 14.4 from 13.5 (I think was the latest release > version?), > > uname output: 14.4-RELEASE-p3 FreeBSD 14.4-RELEASE-p3 GENERIC amd64 > > > > > > When I try to build ports now, this is what I keep getting: > > > > > > ===>>> Creating a backup package for old version portmaster-3.35 > > Creating package for portmaster-3.35 > > pkg-static: file > '/usr/local/share/licenses/portmaster-3.35/BSD2CLAUSE' > > is missing > > pkg-static: package creation failed > > > > ===>>> Package creation failed for portmaster-3.35! > > > > ===>>> Ignore this error [i] > > ===>>> Abort update [a] > > ===>>> Retry [r] > > > > ===>>> How would you like to proceed? [i] > > > > No packages matched for pattern 'portmaster-3.35' > > > > Checking integrity... done (0 conflicting) > > 1 packages requested for removal: 0 locked, 1 missing > > > > ===> Installing for portmaster-3.35 > > ===> Checking if portmaster is already installed > > ===> portmaster-3.35 is already installed > > You may wish to ``make deinstall'' and install this port > again > > by ``make reinstall'' to upgrade it properly. > > If you really wish to overwrite the old port of portmaster > > without deleting it first, set the variable > "FORCE_PKG_REGISTER" > > in your environment or the "make install" command line. > > *** Error code 1 > > > > Stop. > > make[1]: stopped making "/usr/ports/ports-mgmt/portmaster/ > > work/.install_done.portmaster._usr_local" in /usr/ports/ports-mgmt/ > > portmaster > > *** Error code 1 > > > > Stop. > > make: stopped making "install" in /usr/ports/ports-mgmt/portmaster > > > > ===>>> A backup package for portmaster-3.35 should > > be located in /usr/ports/packages/portmaster-backup > > > > ===>>> Installation of portmaster-3.35 (ports-mgmt/portmaster) > failed > > ===>>> Aborting update > > > > > > ===>>> You can restart from the point of failure with this > command line: > > portmaster <flags> ports-mgmt/portmaster > > > > This command has been saved to ~/portmasterfail.txt > > > > > > > > For some reason I'm unable to use either portmaster or even the > standard > > 'make' command under any of the ports eg: > > > > > > :/usr/ports/ports-mgmt/portmaster # make deinstall; make install > clean > > ===> Deinstalling for portmaster > > ===> Deinstalling portmaster-3.35 > > Checking integrity... done (0 conflicting) > > Deinstallation has been requested for the following 1 packages > (of 0 > > packages in the universe): > > > > Installed packages to be REMOVED: > > portmaster: 3.33 > > > > Number of packages to be removed: 1 > > [1/1] Deinstalling portmaster-3.33... > > [1/1] Deleting files for portmaster-3.33: 100% > > ===> Installing for portmaster-3.35 > > ===> Checking if portmaster is already installed > > ===> portmaster-3.35 is already installed > > You may wish to ``make deinstall'' and install this port > again > > by ``make reinstall'' to upgrade it properly. > > If you really wish to overwrite the old port of portmaster > > without deleting it first, set the variable > "FORCE_PKG_REGISTER" > > in your environment or the "make install" command line. > > *** Error code 1 > > > > Stop. > > make[1]: stopped making "/usr/ports/ports-mgmt/portmaster/ > > work/.install_done.portmaster._usr_local" in /usr/ports/ports-mgmt/ > > portmaster > > *** Error code 1 > > > > Stop. > > make: stopped making "install clean" in > /usr/ports/ports-mgmt/portmaster > > > > > > There's a mismatch somewhere but what's going on? > > The ports tree, and therefore portmaster, perform installs and > uninstalls by running pkg. Running `pkg query %v portmaster` should > display what is says is currently the installed version number. If > it is > installed according to pkg, then `pkg delete portmaster` should be > the > correct action to remove it. `pkg info` outputs all installed > packages > with version on the package name and comment beside it if you want to > manually review your full list. > I'm not sure what would have brought it to a state of always > removing > pkg 3.33 when the ports tree and/or portmaster says it is > uninstalling > 3.35 before that. I'd guess just an output bug where they assume > its the > same version but that is misleading if that is happening and > deserves a > bug report; better to display no version number on a stage's > output if > the output is going to not match the command. > > > Do I need to update the ports tree? It seems there is no more > "portsnap" > > command so should I clean out /usr/ports completely then use the > git > > version described here: > > You should decide if there is anything in there that you want > backed > up first: distfiles will only be used by a port calling for them and > generally require size and checksum match to be used so should be > safe > to keep and will save download time/bandwidth. Work directories of > many > ports get a versioned folder inside of it but the ports tree > instructions don't check that what already exists is correct; in any > case I'd let them all go if builds are giving you trouble (just as > 'make > clean' would have done in a port's folder). > > > https://docs.freebsd.org/en/books/handbook/ports/ > > > > > > I guess this would be needed: # git clone --depth 1 https:// > > git.FreeBSD.org/ports.git <http://git.FreeBSD.org/ports.git>; > /usr/ports ? > > I don't use '--depth 1' when I use git but seeing that discussed > seems vaguely familiar. As I do want git history to be accurate and > complete and I do make changes to the ports tree and with the > intention > of submitting patches I create it without that part. I migrated > when use > of git was still fairly new and I didn't reread that whole > document but > I recall I had /usr/ports as its own ZFS dataset and git gave me > grief > in trying to clone to that location, probably caused by the > existence of > /usr/ports/.zfs but I forget). I think there is another flag that > suppresses such complaint but I think I cloned it to another location > that was a normal directory and moved its contents including hidden > content to /usr/ports. Git maintains its own data (only?) in > /usr/ports/.git so that must be transferred too if moving the clone. > > > Regards, > > > > > > Kaya > [-- Attachment #2 --] <!DOCTYPE html> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> <p>Hi,</p> <p><br> </p> <div class="moz-cite-prefix">On 5/26/26 9:23 PM, Maku Bex wrote:<br> </div> <blockquote type="cite" cite="mid:CALvWPyawLXn6eawFjud953UCQvZHbkFZ9_EEeEeaazR9EsoujQ@mail.gmail.com"> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> <div dir="auto">You ran the commands under '/usr/ports' instead of '/usr/ports/ports-mgmt/portmaster'. You need to `cd` to the port name's folder then run the commands. In your case: <div dir="auto"><br> </div> <div dir="auto"># cd /usr/ports/ports-mgmt/portmaster</div> <div dir="auto"># make check-plist && make stage-qa</div> </div> <br> </blockquote> <p><br> </p> <p>Sorry I think I just blindly followed instructions or misunderstood as I had been awake for a little too long.</p> <p><br> </p> <p>Some good news, after removing and re-fetching the ports tree, I was able to rebuild Portmaster through using the standard "make" command and portmaster itself.</p> <p><br> </p> <p>At the moment, I've just done a: portmaster -adyf --no-confirm</p> <p><br> </p> <p>hopefully if the @ports system has stabilized now it should be able to complete the build of Perl which it got stuck on. Currently it's on 9 out of 828 ports, so maybe in a few hours once it gets to say port 11 or something where Perl gets rebuilt I should know.</p> <p><br> </p> <p>The machine is only a quad core Xeon so this will take some time but hopefully now it will build?</p> <p><br> </p> <p>I'll keep everyone posted :-)</p> <p><br> </p> <p>Regards,</p> <p><br> </p> <p>Kaya</p> <p><br> </p> <blockquote type="cite" cite="mid:CALvWPyawLXn6eawFjud953UCQvZHbkFZ9_EEeEeaazR9EsoujQ@mail.gmail.com"> <div class="gmail_quote gmail_quote_container"> <div dir="ltr" class="gmail_attr">On Tue, May 26, 2026, 14:31 Edward Sanford Sutton, III <<a href="mailto:mirror176@hotmail.com" moz-do-not-send="true" class="moz-txt-link-freetext">mirror176@hotmail.com</a>> wrote:<br> </div> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 5/25/26 22:43, Kaya Saman wrote:<br> > Hi,<br> > <br> > <br> > I've just gone through the upgrade procedure described here:<br> > <br> > <br> > <a href="https://docs.freebsd.org/en/books/handbook/cutting-edge/" rel="noreferrer noreferrer" target="_blank" moz-do-not-send="true" class="moz-txt-link-freetext">https://docs.freebsd.org/en/books/handbook/cutting-edge/</a><br>; > <br> > <br> > and updated to 14.4 from 13.5 (I think was the latest release version?), <br> > uname output: 14.4-RELEASE-p3 FreeBSD 14.4-RELEASE-p3 GENERIC amd64<br> > <br> > <br> > When I try to build ports now, this is what I keep getting:<br> > <br> > <br> > ===>>> Creating a backup package for old version portmaster-3.35<br> > Creating package for portmaster-3.35<br> > pkg-static: file '/usr/local/share/licenses/portmaster-3.35/BSD2CLAUSE' <br> > is missing<br> > pkg-static: package creation failed<br> > <br> > ===>>> Package creation failed for portmaster-3.35!<br> > <br> > ===>>> Ignore this error [i]<br> > ===>>> Abort update [a]<br> > ===>>> Retry [r]<br> > <br> > ===>>> How would you like to proceed? [i]<br> > <br> > No packages matched for pattern 'portmaster-3.35'<br> > <br> > Checking integrity... done (0 conflicting)<br> > 1 packages requested for removal: 0 locked, 1 missing<br> > <br> > ===> Installing for portmaster-3.35<br> > ===> Checking if portmaster is already installed<br> > ===> portmaster-3.35 is already installed<br> > You may wish to ``make deinstall'' and install this port again<br> > by ``make reinstall'' to upgrade it properly.<br> > If you really wish to overwrite the old port of portmaster<br> > without deleting it first, set the variable "FORCE_PKG_REGISTER"<br> > in your environment or the "make install" command line.<br> > *** Error code 1<br> > <br> > Stop.<br> > make[1]: stopped making "/usr/ports/ports-mgmt/portmaster/ <br> > work/.install_done.portmaster._usr_local" in /usr/ports/ports-mgmt/ <br> > portmaster<br> > *** Error code 1<br> > <br> > Stop.<br> > make: stopped making "install" in /usr/ports/ports-mgmt/portmaster<br> > <br> > ===>>> A backup package for portmaster-3.35 should<br> > be located in /usr/ports/packages/portmaster-backup<br> > <br> > ===>>> Installation of portmaster-3.35 (ports-mgmt/portmaster) failed<br> > ===>>> Aborting update<br> > <br> > <br> > ===>>> You can restart from the point of failure with this command line:<br> > portmaster <flags> ports-mgmt/portmaster<br> > <br> > This command has been saved to ~/portmasterfail.txt<br> > <br> > <br> > <br> > For some reason I'm unable to use either portmaster or even the standard <br> > 'make' command under any of the ports eg:<br> > <br> > <br> > :/usr/ports/ports-mgmt/portmaster # make deinstall; make install clean<br> > ===> Deinstalling for portmaster<br> > ===> Deinstalling portmaster-3.35<br> > Checking integrity... done (0 conflicting)<br> > Deinstallation has been requested for the following 1 packages (of 0 <br> > packages in the universe):<br> > <br> > Installed packages to be REMOVED:<br> > portmaster: 3.33<br> > <br> > Number of packages to be removed: 1<br> > [1/1] Deinstalling portmaster-3.33...<br> > [1/1] Deleting files for portmaster-3.33: 100%<br> > ===> Installing for portmaster-3.35<br> > ===> Checking if portmaster is already installed<br> > ===> portmaster-3.35 is already installed<br> > You may wish to ``make deinstall'' and install this port again<br> > by ``make reinstall'' to upgrade it properly.<br> > If you really wish to overwrite the old port of portmaster<br> > without deleting it first, set the variable "FORCE_PKG_REGISTER"<br> > in your environment or the "make install" command line.<br> > *** Error code 1<br> > <br> > Stop.<br> > make[1]: stopped making "/usr/ports/ports-mgmt/portmaster/ <br> > work/.install_done.portmaster._usr_local" in /usr/ports/ports-mgmt/ <br> > portmaster<br> > *** Error code 1<br> > <br> > Stop.<br> > make: stopped making "install clean" in /usr/ports/ports-mgmt/portmaster<br> > <br> > <br> > There's a mismatch somewhere but what's going on?<br> <br> The ports tree, and therefore portmaster, perform installs and <br> uninstalls by running pkg. Running `pkg query %v portmaster` should <br> display what is says is currently the installed version number. If it is <br> installed according to pkg, then `pkg delete portmaster` should be the <br> correct action to remove it. `pkg info` outputs all installed packages <br> with version on the package name and comment beside it if you want to <br> manually review your full list.<br> I'm not sure what would have brought it to a state of always removing <br> pkg 3.33 when the ports tree and/or portmaster says it is uninstalling <br> 3.35 before that. I'd guess just an output bug where they assume its the <br> same version but that is misleading if that is happening and deserves a <br> bug report; better to display no version number on a stage's output if <br> the output is going to not match the command.<br> <br> > Do I need to update the ports tree? It seems there is no more "portsnap" <br> > command so should I clean out /usr/ports completely then use the git <br> > version described here:<br> <br> You should decide if there is anything in there that you want backed <br> up first: distfiles will only be used by a port calling for them and <br> generally require size and checksum match to be used so should be safe <br> to keep and will save download time/bandwidth. Work directories of many <br> ports get a versioned folder inside of it but the ports tree <br> instructions don't check that what already exists is correct; in any <br> case I'd let them all go if builds are giving you trouble (just as 'make <br> clean' would have done in a port's folder).<br> <br> > <a href="https://docs.freebsd.org/en/books/handbook/ports/" rel="noreferrer noreferrer" target="_blank" moz-do-not-send="true" class="moz-txt-link-freetext">https://docs.freebsd.org/en/books/handbook/ports/</a><br>; > <br> > <br> > I guess this would be needed: # git clone --depth 1 https:// <br> > <a href="http://git.FreeBSD.org/ports.git" rel="noreferrer noreferrer" target="_blank" moz-do-not-send="true">git.FreeBSD.org/ports.git</a> /usr/ports ?<br> <br> I don't use '--depth 1' when I use git but seeing that discussed <br> seems vaguely familiar. As I do want git history to be accurate and <br> complete and I do make changes to the ports tree and with the intention <br> of submitting patches I create it without that part. I migrated when use <br> of git was still fairly new and I didn't reread that whole document but <br> I recall I had /usr/ports as its own ZFS dataset and git gave me grief <br> in trying to clone to that location, probably caused by the existence of <br> /usr/ports/.zfs but I forget). I think there is another flag that <br> suppresses such complaint but I think I cloned it to another location <br> that was a normal directory and moved its contents including hidden <br> content to /usr/ports. Git maintains its own data (only?) in <br> /usr/ports/.git so that must be transferred too if moving the clone.<br> <br> > Regards,<br> > <br> > <br> > Kaya<br> <br> </blockquote> </div> </blockquote> </body> </html>home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1cc06f0d-d10c-44bc-90de-bf1e1c1a61ea>