FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ devel/py-spyder | 3.2.7 | v4.2.2 +-+ science/afni| 21.0.08 | afni_21.0.09 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Reported by:portscout! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: sysutils/uefi-edk2-bhyve isssue
On Mon, Feb 22, 2021 at 11:30:24PM -0700, Rebecca Cran wrote: > On 2/22/2021 9:21 PM, Rebecca Cran wrote: > > On 2/22/2021 8:43 AM, The Doctor wrote: > > > >> Same result and now looking to reinstall gcc48 > >> in the csm version! > > > > I just installed a fresh copy of FreeBSD 12.2 and ran 'make' in > > /usr/ports/sysutils/uefi-edk2-bhyve and it completed without any errors. > > > > I'm trying using synth next. > > That worked too. > > Do you have anything in /etc/make.conf that could be affecting the build? > > > -- > Rebecca Cran > > DEFAULT_VERSIONS+=linux=c7_64 DEFAULT_VERSIONS+=ruby=2.7 DEFAULT_VERSIONS+=python=3.8 DEFAULT_VERSIONS+=pytho3=3.8 DEFAULT_VERSIONS+=bdb=5.3 DEFAULT_VERSIONS+=lua=5.3 DEFAULT_VERSIONS+=perl5=5.30 DEFAULT_VERSIONS+=ssl=openssl DEFAULT_VERSIONS+=gcc=10 HAVE_MOTIF=yes CC=/usr/local/bin/clang11 C++=/usr/local/bin/clang++11 CXX=/usr/local/bin/clang++11 CPP=/usr/local/bin/clang-cpp11 MAKE_JOBS_NUMBER=1 SUEXEC_DOCROOT=/usr/home SUEXEC_USERDIR=html SUEXEC_GID_MIN=100 SUEXEC_UID_MIN=100 -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising! Look at Psalms 14 and 53 on Atheism https://www.empire.kred/ROOTNK?t=94a1f39b NFLD on 13 Feb vote Liberal ! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: sysutils/uefi-edk2-bhyve isssue
On 2/23/21 7:49 AM, The Doctor wrote: On Mon, Feb 22, 2021 at 11:30:24PM -0700, Rebecca Cran wrote: Do you have anything in /etc/make.conf that could be affecting the build? DEFAULT_VERSIONS+=linux=c7_64 DEFAULT_VERSIONS+=ruby=2.7 DEFAULT_VERSIONS+=python=3.8 DEFAULT_VERSIONS+=pytho3=3.8 DEFAULT_VERSIONS+=bdb=5.3 DEFAULT_VERSIONS+=lua=5.3 DEFAULT_VERSIONS+=perl5=5.30 DEFAULT_VERSIONS+=ssl=openssl DEFAULT_VERSIONS+=gcc=10 HAVE_MOTIF=yes CC=/usr/local/bin/clang11 C++=/usr/local/bin/clang++11 CXX=/usr/local/bin/clang++11 CPP=/usr/local/bin/clang-cpp11 MAKE_JOBS_NUMBER=1 SUEXEC_DOCROOT=/usr/home SUEXEC_USERDIR=html SUEXEC_GID_MIN=100 SUEXEC_UID_MIN=100 Could you try removing or commenting out the CC, C++, CXX and CPP lines please? -- Rebecca Cran ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: sysutils/uefi-edk2-bhyve isssue
On 23/02/2021 15:49, The Doctor via freebsd-ports wrote: DEFAULT_VERSIONS+=linux=c7_64 DEFAULT_VERSIONS+=ruby=2.7 DEFAULT_VERSIONS+=python=3.8 DEFAULT_VERSIONS+=pytho3=3.8 This looks like a typo BTW. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
When did pkg(8) drop support for 12-STABLE?
OK On a virgin 12 stable install. Followed by a svnlite co svn://svn.freebsd.org/portd/head /usr/ports and a /usr/src already populated. A trip to /usr/ports/ports-mgmt/pkg followed by make install clean returned: /!\ ERROR: /!\ Ports Collection support for your FreeBSD version has ended, and no ports are guaranteed to build on this system. Please upgrade to a supported release. No support will be provided if you silence this message by defining ALLOW_UNSUPPORTED_SYSTEM. *** Error code 1 Stop. While I could follow pkg's suggested alternative. This all just seems very wrong. Is there any way to disable pkg completely. So I can simply build ports, rather than packages? maybe a WITH_PKG=false USE_PKG=false or something else? Thanks in advance for any enlightenment. --Chris ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Updating emulators/i386-wine-devel but get a runtime error
Hi freebsd-ports@ I recently adopted emulators/i386-wine-devel and am attempting to update it to 6.2 along with adding 14.0 support. Phabricator URL: https://reviews.freebsd.org/D28908 When I attempt to run the `wine` command, I get this error: root@omen:/usr/ports.dev/emulators/i386-wine-devel # wine wine: could not load ntdll.so: (null) root@omen:/usr/ports.dev/emulators/i386-wine-devel # It seems ntdll.so is a new DLL. For anyone who has worked with Wine, is there a reason why this is happening and how I can solve this? -Neel signature.asc Description: OpenPGP digital signature
Re: When did pkg(8) drop support for 12-STABLE?
On 23 Feb 2021, at 13:26, Chris wrote: > OK On a virgin 12 stable install. The current release is 12.2-RELEASE. 12.0-RELEASE was EOLed last February. I am not sure what build you mean by "12-STABLE" Are you on the http://lists.freebsd.org/mailman/listinfo/freebsd-stable mailing list? -- 'Why?' he [Rincewind] said. The world is going to end. 'What, again?' ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Updating emulators/i386-wine-devel but get a runtime error
Nevermind, it was that WINEDLLPATH was missing. -Neel On 2021-02-23 13:01, Neel Chauhan wrote: Hi freebsd-ports@ I recently adopted emulators/i386-wine-devel and am attempting to update it to 6.2 along with adding 14.0 support. Phabricator URL: https://reviews.freebsd.org/D28908 When I attempt to run the `wine` command, I get this error: root@omen:/usr/ports.dev/emulators/i386-wine-devel # wine wine: could not load ntdll.so: (null) root@omen:/usr/ports.dev/emulators/i386-wine-devel # It seems ntdll.so is a new DLL. For anyone who has worked with Wine, is there a reason why this is happening and how I can solve this? -Neel ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: When did pkg(8) drop support for 12-STABLE?
On 2021-02-23 14:58, @lbutlr wrote: On 23 Feb 2021, at 13:26, Chris wrote: OK On a virgin 12 stable install. The current release is 12.2-RELEASE. 12.0-RELEASE was EOLed last February. I am not sure what build you mean by "12-STABLE" It was from a 12-STABLE usb stick (probably 12.1). Is there no way forward, save building up to 12.2? Are you on the http://lists.freebsd.org/mailman/listinfo/freebsd-stable mailing list? Yep. But subscribed under a different email address. Guess I should look into it. Thank you very much for taking the time to reply! --Chris ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: When did pkg(8) drop support for 12-STABLE?
Chris portmaster at bsdforge.com wrote on Tue Feb 23 23:31:09 UTC 2021 : > On 2021-02-23 14:58, @lbutlr wrote: > > On 23 Feb 2021, at 13:26, Chris wrote: > >> OK On a virgin 12 stable install. > > > > The current release is 12.2-RELEASE. 12.0-RELEASE was EOLed last February. > > I > > am > > not sure what build you mean by "12-STABLE" > It was from a 12-STABLE usb stick (probably 12.1). Is there no way forward, > save > building up to 12.2? You might want to report the output of: # uname -apKU if you can still run it in the environment in question. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: sysutils/uefi-edk2-bhyve isssue
On Tue, Feb 23, 2021 at 08:31:18AM -0700, Rebecca Cran wrote: > On 2/23/21 7:49 AM, The Doctor wrote: > > On Mon, Feb 22, 2021 at 11:30:24PM -0700, Rebecca Cran wrote: > > >> Do you have anything in /etc/make.conf that could be affecting the build? > > > > DEFAULT_VERSIONS+=linux=c7_64 > > DEFAULT_VERSIONS+=ruby=2.7 > > DEFAULT_VERSIONS+=python=3.8 > > DEFAULT_VERSIONS+=pytho3=3.8 > > DEFAULT_VERSIONS+=bdb=5.3 > > DEFAULT_VERSIONS+=lua=5.3 > > DEFAULT_VERSIONS+=perl5=5.30 > > DEFAULT_VERSIONS+=ssl=openssl > > DEFAULT_VERSIONS+=gcc=10 > > HAVE_MOTIF=yes > > CC=/usr/local/bin/clang11 > > C++=/usr/local/bin/clang++11 > > CXX=/usr/local/bin/clang++11 > > CPP=/usr/local/bin/clang-cpp11 > > MAKE_JOBS_NUMBER=1 > > SUEXEC_DOCROOT=/usr/home > > SUEXEC_USERDIR=html > > SUEXEC_GID_MIN=100 > > SUEXEC_UID_MIN=100 > > > > Could you try removing or commenting out the CC, C++, CXX and CPP lines > please? > > -- > Rebecca Cran > Same result. -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising! Look at Psalms 14 and 53 on Atheism https://www.empire.kred/ROOTNK?t=94a1f39b NFLD on 13 Feb vote Liberal ! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: sysutils/uefi-edk2-bhyve isssue
On Tue, Feb 23, 2021 at 08:31:18AM -0700, Rebecca Cran wrote: > On 2/23/21 7:49 AM, The Doctor wrote: > > On Mon, Feb 22, 2021 at 11:30:24PM -0700, Rebecca Cran wrote: > > >> Do you have anything in /etc/make.conf that could be affecting the build? > > > > DEFAULT_VERSIONS+=linux=c7_64 > > DEFAULT_VERSIONS+=ruby=2.7 > > DEFAULT_VERSIONS+=python=3.8 > > DEFAULT_VERSIONS+=pytho3=3.8 > > DEFAULT_VERSIONS+=bdb=5.3 > > DEFAULT_VERSIONS+=lua=5.3 > > DEFAULT_VERSIONS+=perl5=5.30 > > DEFAULT_VERSIONS+=ssl=openssl > > DEFAULT_VERSIONS+=gcc=10 > > HAVE_MOTIF=yes > > CC=/usr/local/bin/clang11 > > C++=/usr/local/bin/clang++11 > > CXX=/usr/local/bin/clang++11 > > CPP=/usr/local/bin/clang-cpp11 > > MAKE_JOBS_NUMBER=1 > > SUEXEC_DOCROOT=/usr/home > > SUEXEC_USERDIR=html > > SUEXEC_GID_MIN=100 > > SUEXEC_UID_MIN=100 > > > > Could you try removing or commenting out the CC, C++, CXX and CPP lines > please? > > -- > Rebecca Cran > Again, same issue. What is causing ld-elf.so.1: /usr/local/lib/compat/libstdc++.so.6: version CXXABI_1.3.8 required +by +/usr/ports/sysutils/uefi-edk2-bhyve/work/edk2-2e1e8c35f3178df95d79da81ac6deec24 +2da74c2/BaseTools/Source/C/bin/VfrCompile not found make[2]: *** [GNUmakefile:315: +/usr/ports/sysutils/uefi-edk2-bhyve/work/Build/BhyveX64/RELEASE_GCC5/X64/MdeMod +ulePkg/Library/BootMaintenanceManagerUiLib/BootMaintenanceManagerUiLib/DEBUG/Bo +otMaintenanceManager.c] Error 1 make[2]: Leaving directory +'/usr/ports/sysutils/uefi-edk2-bhyve/work/Build/BhyveX64/RELEASE_GCC5/X64/MdeMo +dulePkg/Library/BootMaintenanceManagerUiLib/BootMaintenanceManagerUiLib' To take place? -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising! Look at Psalms 14 and 53 on Atheism https://www.empire.kred/ROOTNK?t=94a1f39b NFLD on 13 Feb vote Liberal ! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: When did pkg(8) drop support for 12-STABLE?
On 2021-02-23 16:04, Mark Millard wrote: Chris portmaster at bsdforge.com wrote on Tue Feb 23 23:31:09 UTC 2021 : On 2021-02-23 14:58, @lbutlr wrote: > On 23 Feb 2021, at 13:26, Chris wrote: >> OK On a virgin 12 stable install. > > The current release is 12.2-RELEASE. 12.0-RELEASE was EOLed last February. I > am > not sure what build you mean by "12-STABLE" It was from a 12-STABLE usb stick (probably 12.1). Is there no way forward, save building up to 12.2? You might want to report the output of: # uname -apKU if you can still run it in the environment in question. Thank you for your thoughtful suggestion, Mark. It returns: FreeBSD fbsd12dev 12.1-STABLE FreeBSD 12.1-STABLE r363918 GENERIC amd64 amd64 1201522 1201522 Is that bad? Thanks again. --Chris === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: When did pkg(8) drop support for 12-STABLE?
On Wed, 24 Feb 2021 at 15:00, Chris wrote: > > On 2021-02-23 16:04, Mark Millard wrote: > > Chris portmaster at bsdforge.com wrote on > > Tue Feb 23 23:31:09 UTC 2021 : > > > >> On 2021-02-23 14:58, @lbutlr wrote: > >> > On 23 Feb 2021, at 13:26, Chris wrote: > >> >> OK On a virgin 12 stable install. > >> > > >> > The current release is 12.2-RELEASE. 12.0-RELEASE was EOLed last > >> > February. I > >> > am > >> > not sure what build you mean by "12-STABLE" > >> It was from a 12-STABLE usb stick (probably 12.1). Is there no way forward, > >> save > >> building up to 12.2? > > > > > > You might want to report the output of: > > > > # uname -apKU > > > > if you can still run it in the environment in question. > Thank you for your thoughtful suggestion, Mark. > It returns: > FreeBSD fbsd12dev 12.1-STABLE FreeBSD 12.1-STABLE r363918 GENERIC amd64 > amd64 1201522 1201522 > > Is that bad? You're running 12.1, and not -STABLE. The EOL for 12.1 was Nov-2019. You need to get a later version or run -STABLE (ie: build from source off the stable/12 branch). Cheers. -- Jonathan Chen ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: When did pkg(8) drop support for 12-STABLE?
On 2021-02-23 18:25, Jonathan Chen wrote: On Wed, 24 Feb 2021 at 15:00, Chris wrote: On 2021-02-23 16:04, Mark Millard wrote: > Chris portmaster at bsdforge.com wrote on > Tue Feb 23 23:31:09 UTC 2021 : > >> On 2021-02-23 14:58, @lbutlr wrote: >> > On 23 Feb 2021, at 13:26, Chris wrote: >> >> OK On a virgin 12 stable install. >> > >> > The current release is 12.2-RELEASE. 12.0-RELEASE was EOLed last February. I >> > am >> > not sure what build you mean by "12-STABLE" >> It was from a 12-STABLE usb stick (probably 12.1). Is there no way forward, >> save >> building up to 12.2? > > > You might want to report the output of: > > # uname -apKU > > if you can still run it in the environment in question. Thank you for your thoughtful suggestion, Mark. It returns: FreeBSD fbsd12dev 12.1-STABLE FreeBSD 12.1-STABLE r363918 GENERIC amd64 amd64 1201522 1201522 Is that bad? Thanks for the reply, Jonathan. You're running 12.1, and not -STABLE. The EOL for 12.1 was Nov-2019. Odd. It _says_ it's the STABLE branch. You need to get a later version or run -STABLE (ie: build from source off the stable/12 branch). It _was_ built from the stable/12 branch. All be it a good while ago. I guess I've somehow lost my understanding of what tracking STABLE really means. Or maybe it's changed. But I installed from a 12-STABLE medium. uname(1) reports it's 12-STABLE (12.1-STABLE). But it's _not_ 12-STABLE. See my confusion? :-) Thanks again. --Chris Cheers. -- Jonathan Chen ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: When did pkg(8) drop support for 12-STABLE?
Hello. Jonathan Chen wrote on 2021/02/24 11:25: > > You're running 12.1, and not -STABLE. The EOL for 12.1 was Nov-2019. > > You need to get a later version or run -STABLE (ie: build from source > off the stable/12 branch). No, it's the 12.x-STABLE. But it's older than 12.2-RELEASE. By the way, now 12.x-STABLE needs to bring the source with the following git command. Is there an announcement about it anywhere? git clone -b stable/12 "https://git.FreeBSD.org/src.git"; /usr/src git -C /usr/src/ fetch -- origin stable/12 git -C /usr/src/ merge -- git -C /usr/src/ reset --hard HEAD -- Regards. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: When did pkg(8) drop support for 12-STABLE?
On 2021-Feb-23, at 19:26, Tatsuki Makino wrote: > Hello. > > Jonathan Chen wrote on 2021/02/24 11:25: >> >> You're running 12.1, and not -STABLE. The EOL for 12.1 was Nov-2019. >> >> You need to get a later version or run -STABLE (ie: build from source >> off the stable/12 branch). > > No, it's the 12.x-STABLE. But it's older than 12.2-RELEASE. > > By the way, now 12.x-STABLE needs to bring the source with the following git > command. > Is there an announcement about it anywhere? > > git clone -b stable/12 "https://git.FreeBSD.org/src.git"; /usr/src > git -C /usr/src/ fetch -- origin stable/12 > git -C /usr/src/ merge -- > git -C /usr/src/ reset --hard HEAD -- For only getting 12's source (not for committing source) . . . For stable/12/ and releng/12.*/ and release/12.*.*/ svn can still be used: git use is and will be optional, although svn is somewhat delayed from git for when commits appear. (There was a recent problem that made for a huge delay for svn to have the commits appear. That has been fixed and the delays are back to the normal timescale as I understand.) For stable/13/ and releng/13.*/ and relelase/13.*/ and main (14) and later: snv can no longer be used to get source. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: sysutils/uefi-edk2-bhyve isssue
On 2/23/2021 5:58 PM, The Doctor wrote: Again, same issue. What is causing ld-elf.so.1: /usr/local/lib/compat/libstdc++.so.6: version CXXABI_1.3.8 required +by +/usr/ports/sysutils/uefi-edk2-bhyve/work/edk2-2e1e8c35f3178df95d79da81ac6deec24 +2da74c2/BaseTools/Source/C/bin/VfrCompile not found make[2]: *** [GNUmakefile:315: +/usr/ports/sysutils/uefi-edk2-bhyve/work/Build/BhyveX64/RELEASE_GCC5/X64/MdeMod +ulePkg/Library/BootMaintenanceManagerUiLib/BootMaintenanceManagerUiLib/DEBUG/Bo +otMaintenanceManager.c] Error 1 make[2]: Leaving directory +'/usr/ports/sysutils/uefi-edk2-bhyve/work/Build/BhyveX64/RELEASE_GCC5/X64/MdeMo +dulePkg/Library/BootMaintenanceManagerUiLib/BootMaintenanceManagerUiLib' To take place? I'm fairly sure it means you have _some_ sort of toolchain installation/configuration that's messing things up. Could you run 'make clean' in the uefi-edk2-bhyve directory - then, run 'script bhyve_build_log.txt make' to log all the output to the file 'bhyve_build_log.txt'? And then upload the contents somewhere, for example https://pastebin.com/ . -- Rebecca Cran ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: When did pkg(8) drop support for 12-STABLE?
Mark Millard wrote on 2021/02/24 12:43: > On 2021-Feb-23, at 19:26, Tatsuki Makino wrote: > >> By the way, now 12.x-STABLE needs to bring the source with the following git >> command. >> Is there an announcement about it anywhere? >> >> git clone -b stable/12 "https://git.FreeBSD.org/src.git"; /usr/src >> git -C /usr/src/ fetch -- origin stable/12 >> git -C /usr/src/ merge -- >> git -C /usr/src/ reset --hard HEAD -- > > For only getting 12's source (not for committing source) > . . . > Thank you. I was able to get r368787 and later with svnlite update :) It's a pain to delete /usr/src every time, so I switch it with nullfs. mount -t nullfs /home/svn/FreeBSD/base/stable/12 /usr/src mount -t nullfs /home/git/FreeBSD/src/stable/12 /usr/src Regards. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: When did pkg(8) drop support for 12-STABLE?
Am 24.02.2021 um 00:31 schrieb Chris: It was from a 12-STABLE usb stick (probably 12.1). Is there no way forward, save building up to 12.2? yes: freebsd-update upgrade -r 12.2-RELEASE freebsd-update install # nextboot -k GENERIC reboot freebsd-update install # check that config files in etc are correct! reboot # Make sure you point pkg repo definition to correct FreeBSD version pkg update -f pkg-static install -f pkg pkg-static upgrade -F -y pkg upgrade -f -y freebsd-update install reboot Check for more details the documentation: https://docs.freebsd.org/en/books/handbook/updating-upgrading-freebsdupdate.html Gruß Matthias -- "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning." -- Rich Cook ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
