Date: Sat, 08 Oct 2022 15:33:41 -0700 From: "Pat Maddox" <pat@patmaddox.com> To: questions@freebsd.org Subject: Re: pkg upgrade vs building from source Message-ID: <99bb01a2-e099-4a52-808d-b1e4ec28385f@app.fastmail.com> In-Reply-To: <CAMtcK2qLsodE2QSE7uLZkoRRo7ogHNmfHGJAHTR9g2ZP8HgpfQ@mail.gmail.com> References: <CAMtcK2rPSxd0DignXvzw%2BnNc1U1iYpBjGpN%2BtqA4zevUO4qkQA@mail.gmail.com> <e4544587-50bb-55e8-3284-58a76b3a69f7@freebsd.org> <CAMtcK2rp2JLHpWJbQHv1DQBB8MS3=ro9hbJF0orUEK3rqJ5xLw@mail.gmail.com> <3da3d329-a19d-51cd-0f78-ef77dbf66bfe@holgerdanske.com> <CAMtcK2qLsodE2QSE7uLZkoRRo7ogHNmfHGJAHTR9g2ZP8HgpfQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Do you use pkg only, or do you have a mix of ports and packages? I ask b= ecause you mention going back to ports and it working=E2=80=A6 my unders= tanding is generally you want to use ports xor pkg, not mix them. Also you might consider using latest pkg instead of quarterly, as it=E2=80= =99s going to be more current and thus have any fixes that might not be = in quarterly yet. But if you are mixing ports and pkg, I would start there. It=E2=80=99s p= ossible you have pretty recent ports, mixed with old-ish (quarterly) pkg= , and that could certainly cause issues. Pat On Sat, Oct 8, 2022, at 2:52 PM, paul beard wrote: > freebsd-version -kru ; uname -aKU > 12.3-RELEASE-p6 > 12.3-RELEASE > 12.3-RELEASE-p7 > FreeBSD www.paulbeard.org 12.3-RELEASE FreeBSD 12.3-RELEASE r371126 GE= NERIC > i386 1203000 1203000 > > pkg -vv | grep -e url -e enabled -e priority > url : "pkg+http://pkg.FreeBSD.org/FreeBSD:12:i386/quar= terly > ", > enabled : yes, > priority : 0, > > > On Sat, Oct 8, 2022 at 2:41 PM David Christensen <dpchrist@holgerdansk= e.com> > wrote: > >> On 10/8/22 08:35, paul beard wrote: >> > My skepticism over pkg doing what I expect grows after recent even= ts. >> >> > I allowed [pkg] to upgrade postfix the other day and discovered th= at >> it no longer worked; >> >> > How do other people manage this? >> >> >> I have operated a FreeBSD SOHO server 24x7 for 3+ years, starting with >> FreeBSD-11.2-RELEASE-amd64, I strive to keep my systems as simple and >> "official" as possible. I have never seen any problems that I could >> attribute to freebsd-update(1) or pkg(1). >> >> >> My upgrade mantra is: >> >> # freebsd-update fetch install >> >> # pkg update >> >> # pkg upgrade >> >> # pkg autoremove >> >> # pkg clean >> >> >> On 10/8/22 13:18, paul beard wrote: >> > On 10/8/22 11:11, Graham Perrin wrote: >> >> Which version of FreeBSD, exactly? >> >> >> > FreeBSD www.paulbeard.org 12.3-RELEASE FreeBSD 12.3-RELEASE r371126 >> GENERIC >> > i386 >> > >> > >> >> Packages from latest, or quarterly? >> >> >> > Hm=E2=80=A6whatever pkg update pulls >> >> >> >> freebsd-version -kru ; uname -aKU >> >> >> > See above. >> >> >> For comparison: >> >> 2022-10-08 14:03:04 toor@f3 ~ >> # freebsd-version -kru ; uname -aKU >> 12.3-RELEASE-p6 >> 12.3-RELEASE-p6 >> 12.3-RELEASE-p7 >> FreeBSD f3.tracy.holgerdanske.com 12.3-RELEASE-p6 FreeBSD >> 12.3-RELEASE-p6 GENERIC amd64 1203000 1203000 >> >> >> I do not see any freebsd-version(1) output in your output, above. >> >> >> I do not see a patch level in your uname(1) output, above. >> >> >> The most obvious difference is that you are running i386 and I am >> running amd64. That is not supposed to matter. >> >> >> > pkg -vv | grep -e url -e enabled -e priority >> > >> > url : >> "pkg+http://pkg.FreeBSD.org/FreeBSD:12:i386/quarterly >> > ", >> > enabled : yes, >> > priority : 0, >> >> >> For comparison: >> >> 2022-10-08 14:03:12 toor@f3 ~ >> # pkg -vv | grep -e url -e enabled -e priority >> url : >> "pkg+http://pkg.FreeBSD.org/FreeBSD:12:amd64/quarterly", >> enabled : yes, >> priority : 0, >> >> >> David >> >> > > --=20 > Paul Beard / www.paulbeard.org/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?99bb01a2-e099-4a52-808d-b1e4ec28385f>