Re: Ports recompile for 13.0-RELEASE
On 04 May 2021, at 09:00, Ronald Klop wrote: > On 5/4/21 4:10 PM, @lbutlr wrote: >> With the move to FreeBSD 13.0 is there a simple (single step) way to >> reinstall all the current ports other than saving off a list of the ports >> and then stepping through that list to reinstall them? It was very >> inefficient when moving to 12.0 as many ports in the list, of course, were >> dependent on other ports, but then got recompiled, sometimes multiple times. >> I know I ended up in a make loop where came was compiled over and over again >> until I aborted, listed the current ports, differ on the previous ports, and >> picked a port I though would have a lot of reps to restart the compile. I >> then did this several more times to get back to where I had been on 11.x > > I used "portmaster -fa" in the past. Yeah, that's what I tried wen moving to 12.0 from 11.4 and it left a lot of cleaning up. >> (And yes, I've tried moving to poudrerie several times and we do not get on. >> At all.) > > Might help to do another attempt. Especially if you are using custom port > settings instead of pkgs. It just doesn't work the way my brain works, and I don't have a bunch of servers I need to keep updated, and the two servers I am running are different architecture. Something as simple as "hey, I want to install this one port" seemed overly complicated. I can see it's great when you have a cluster of servers and want to manage the updates on a dedicated server, but I don't need that. That said: # pkg-static upgrade -f # portmaster install postfix dovecot So far, so good (I thought I would have to also redo MariaDB but it all seems to be working now, mail did not work until I recompiled Dovecot and Postfix, but I was expecting that. So far the only thing that is new is an error about pam_opie, but that's for a new thread. -- Incredible! One of the worst performances of my career and they never doubted it for a second. ___ 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: Ports recompile for 13.0-RELEASE
On 2021-05-04 07:10, @lbutlr wrote: With the move to FreeBSD 13.0 is there a simple (single step) way to reinstall all the current ports other than saving off a list of the ports and then stepping through that list to reinstall them? It was very inefficient when moving to 12.0 as many ports in the list, of course, were dependent on other ports, but then got recompiled, sometimes multiple times. I know I ended up in a make loop where came was compiled over and over again until I aborted, listed the current ports, differ on the previous ports, and picked a port I though would have a lot of reps to restart the compile. I then did this several more times to get back to where I had been on 11.x And there's still no way to tell if a port was installed from pkg or from ports, correct? Since I use MariaDB instead of MySQLI have to be sure I don't try to use package for anything that will try to install MySQL instead. And finally, the release of 13.0 ends the 12.x versions, right? There will not be a 12.3. (And yes, I've tried moving to poudrerie several times and we do not get on. At all.) Not a big fan of poudrerie. If I must, I generally choose synth. But try to avoid both if at all possible. jail(8) is my go-to for most things they try to facilitate. While this isn't the simple "set it, and forget it" solution you seek. I find that picking a meta-port/package as part of something I'm installing, gets me pretty close to all I need. The key to my method is the "recursive" keyword. IOW # cd /usr/ports/x11/xorg/ # make config-recursive (repeat this until dialog stops appearing) When complete # make package-recursive (install) clean If I'm in my build jail and have a /usr/ports/packages/(All|latest) I (ultimately) end up with a nice package repo that facilitates an image install or upgrade path from a fresh install. HTH --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: Ports recompile for 13.0-RELEASE
From: Yasuhiro Kimura Subject: Re: Ports recompile for 13.0-RELEASE Date: Wed, 05 May 2021 00:15:39 +0900 (JST) > It depends on how there are installed. If they are installed by using > official pakcages or building personal packages with poudriere, then > `pkg upgrade` is worth trying. Oops, it should be `pkg upgrade -f`. --- Yasuhiro Kimura ___ 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: Ports recompile for 13.0-RELEASE
From: "@lbutlr" Subject: Ports recompile for 13.0-RELEASE Date: Tue, 4 May 2021 08:10:38 -0600 > With the move to FreeBSD 13.0 is there a simple (single step) way to > reinstall all the current ports other than saving off a list of the > ports and then stepping through that list to reinstall them? It depends on how there are installed. If they are installed by using official pakcages or building personal packages with poudriere, then `pkg upgrade` is worth trying. But you should save list of installed packages just in case. otherwise (i.e. you used portmaster or simple `cd /usr/port/category/portname; make insall`) `portmaster -af` may work fine if you are lucky. But in this case I think saving list of installed packages, removing all of them and then reinstalling them is probably the easiest and shortest way as a result. > And finally, the release of 13.0 ends the 12.x versions, right? > There will not be a 12.3. According to 'Supported FreeBSD releases' (https://www.freebsd.org/security/#sup), expected EoL of 12.2-RELEASE is '12.3-RELEASE + 3 months', and that of stable/12 is June 30, 2024. So at least 12.3-RELEASE will be released. And probably 12.4-RELEASE will be too. --- Yasuhiro Kimura ___ 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: Ports recompile for 13.0-RELEASE
On Tue, May 04, 2021 at 08:10:38AM -0600, @lbutlr wrote: > With the move to FreeBSD 13.0 is there a simple (single step) way to > reinstall all the current ports other than saving off a list of the ports and > then stepping through that list to reinstall them? It was very inefficient > when moving to 12.0 as many ports in the list, of course, were dependent on > other ports, but then got recompiled, sometimes multiple times. I know I > ended up in a make loop where came was compiled over and over again until I > aborted, listed the current ports, differ on the previous ports, and picked a > port I though would have a lot of reps to restart the compile. I then did > this several more times to get back to where I had been on 11.x > > And there's still no way to tell if a port was installed from pkg or from > ports, correct? Since I use MariaDB instead of MySQLI have to be sure I don't > try to use package for anything that will try to install MySQL instead. > > And finally, the release of 13.0 ends the 12.x versions, right? There will > not be a 12.3. > > (And yes, I've tried moving to poudrerie several times and we do not get on. > At all.) If you can get everything into a pkg repo, "pkg upgrade -f" should reinstall everything regardless of if pkg thinks it needs to. I suspect that your problem is minimum proper rebuilding rather than reinstallation. I just keep a list of packages I want (vs all build dependencies), which made my what-needs-rebuilding list much smaller (the dependency list is huge, but I didn't need to track that). I have a list of 58 packages I want installed, but have 494 packages installed for dependencies and I think the build total (some build dependencies don't get installed) is 600+. Your story is reminding me about my portmaster problems back in the day (that drove me to try poudriere, not get it, try synth, then run on synth until I ran into other issues (arm64) that remotivated me to learn poudriere). I know there is someone that has tried to fix portmaster in the meantime, but I think the basic issue is that there are, and will continue to be, issues with incompatible build dependencies that are "solved" by clean-room build systems which are probably the cause of some of those make loops. The last time I had this conversation, someone who had been beating on portmaster spoke up about the work they'd been doing to try and get the clean-room work added to it, but I don't know about the status of that. I think you're going to be aggravated until you find a ports management fix that works for you. ___ 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: Ports recompile for 13.0-RELEASE
On 5/4/21 4:10 PM, @lbutlr wrote: With the move to FreeBSD 13.0 is there a simple (single step) way to reinstall all the current ports other than saving off a list of the ports and then stepping through that list to reinstall them? It was very inefficient when moving to 12.0 as many ports in the list, of course, were dependent on other ports, but then got recompiled, sometimes multiple times. I know I ended up in a make loop where came was compiled over and over again until I aborted, listed the current ports, differ on the previous ports, and picked a port I though would have a lot of reps to restart the compile. I then did this several more times to get back to where I had been on 11.x I used "portmaster -fa" in the past. (see ports-mgmt/portmaster) And there's still no way to tell if a port was installed from pkg or from ports, correct? Since I use MariaDB instead of MySQLI have to be sure I don't try to use package for anything that will try to install MySQL instead. I don't know. And finally, the release of 13.0 ends the 12.x versions, right? There will not be a 12.3. https://www.freebsd.org/security/#sup 12.x has support until 2024. So a 12.3 is in the pipeline. 12.4 probably also. 11.4 was the latest 11.x release AFAIK. (And yes, I've tried moving to poudrerie several times and we do not get on. At all.) Might help to do another attempt. Especially if you are using custom port settings instead of pkgs. Regards, Ronald. ___ 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: Ports recompile for 13.0-RELEASE
On Tue, 4 May 2021 08:10:38 -0600
"@lbutlr" wrote:
> With the move to FreeBSD 13.0 is there a simple (single step) way to
> reinstall all the current ports other than saving off a list of the
> ports and then stepping through that list to reinstall them?
> It was very inefficient when moving to 12.0 as many ports in the
> list, of course, were dependent on other ports, but then got
> recompiled, sometimes multiple times. I know I ended up in a make
> loop where came was compiled over and over again until I aborted,
> listed the current ports, differ on the previous ports, and picked a
> port I though would have a lot of reps to restart the compile. I then
> did this several more times to get back to where I had been on 11.x
Using a local poudriere repo fixes all of the above ;)
>
> And there's still no way to tell if a port was installed from pkg or
> from ports, correct? Since I use MariaDB instead of MySQLI have to be
> sure I don't try to use package for anything that will try to install
> MySQL instead.
The repository the package came from is stored in the annotation tag
named "repository".
You can see this, e.g., by using
pkg query "%n %At %Av"
or
pkg info -R
By default this is "FreeBSD" for the official repos. If you install
locally ("make install"), it's not set.
>
> And finally, the release of 13.0 ends the 12.x versions, right? There
> will not be a 12.3.
See https://www.freebsd.org/security/#sup, there will be a 12.3.
>
> (And yes, I've tried moving to poudrerie several times and we do not
> get on. At all.)
Well, that's the recommended way of doing what you're trying to
accomplish, otherwise you'll be in dependency hell like we've all
been updating our machines in the 2000s.
Alternatively, you could create a jail or VM manually, install all
packages you need in there from ports using make install. You
can retrieve the list of what you need on your target host using
pkg query -e "%a = 0" %o
Then run "pkg create -a" on that machine to get a set of all binary
packages. Then copy those over to your target machine and install them
using pkg add. Will be messy, but kind of work. I really would prefer
poudriere over that though.
Best
Michael
--
Michael Gmelin
___
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"
Ports recompile for 13.0-RELEASE
With the move to FreeBSD 13.0 is there a simple (single step) way to reinstall all the current ports other than saving off a list of the ports and then stepping through that list to reinstall them? It was very inefficient when moving to 12.0 as many ports in the list, of course, were dependent on other ports, but then got recompiled, sometimes multiple times. I know I ended up in a make loop where came was compiled over and over again until I aborted, listed the current ports, differ on the previous ports, and picked a port I though would have a lot of reps to restart the compile. I then did this several more times to get back to where I had been on 11.x And there's still no way to tell if a port was installed from pkg or from ports, correct? Since I use MariaDB instead of MySQLI have to be sure I don't try to use package for anything that will try to install MySQL instead. And finally, the release of 13.0 ends the 12.x versions, right? There will not be a 12.3. (And yes, I've tried moving to poudrerie several times and we do not get on. At all.) -- I don't need no stinking taglines. ___ 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"
