Date: Tue, 3 Dec 2024 18:01:51 -0500 From: Juan Manuel Palacios <jmpalacios@gmail.com> To: fatty.merchandise677@aceecat.org Cc: questions@freebsd.org Subject: Re: postgresql 16 Message-ID: <B8BEA61A-2D54-41E1-B533-F5B553E6F5BC@gmail.com> In-Reply-To: <CwXDBXCeGRTht03G@aceecat.org> References: <6cKxpppDaTNpexhV@aceecat.org> <abc9e458-9305-40b0-bc58-ec1dd3d636dc@fechner.net> <3bc92b40-205f-4da1-ab9c-d3ae5bb5ab1a@netfence.it> <CwXDBXCeGRTht03G@aceecat.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_F841E360-B03F-4903-93DF-85520A2D7E58
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=utf-8
MFH stands for =E2=80=9Cmerged from HEAD=E2=80=9D, which is FreeBSD =
parlance for merging some changeset from the HEAD of some Git branch, =
most usually =E2=80=9Cmain=E2=80=9D, into some other branch, in this =
case one of the ports quarterly branches.
This applies to the conversation at hand because, as you may know, =
FreeBSD offers binary packages either from a =E2=80=9Cquarterly=E2=80=9D =
repository, i.e.:
-> cat /etc/pkg/FreeBSD.conf=20
(=E2=80=A6)
FreeBSD: {
url: "pkg+https://pkg.FreeBSD.org/${ABI}/quarterly",
mirror_type: "srv",
signature_type: "fingerprints",
fingerprints: "/usr/share/keys/pkg",
enabled: yes
}
which is currently pulling from the ports tree=E2=80=99s 2024Q4 branch, =
or from a =E2=80=9Clatest=E2=80=9D repository, which always builds =
directly from the tip of the ports tree=E2=80=99s main branch (hence the =
name). At the tip of the 2024Q4 branch the PostgreSQL ports are =
currently at 16.4, and the bump to 16.6 hasn=E2=80=99t been =
=E2=80=9CMFH=E2=80=99d=E2=80=9D into 2024Q4; that is why no amount of =
=E2=80=9Cpkg update && pkg upgrade=E2=80=9D will ever show you any =
updates for those packages, at least not until an MFH occurs, if it =
does, or a new =E2=80=9Cquarterly=E2=80=9D branch is cut, e.g. 2025Q1 =
(whenever that happens), and the upstream builders switch the =
=E2=80=9Cquarterly=E2=80=9D repo to it.
As for how you=E2=80=99d install *only* the updated PostgreSQL packages =
from the latest repository, while keeping the rest of your system on =
quarterly, I guess that could be achieved by some combination of:
1. mkdir -pv /usr/local/etc/pkg/repos
2. echo 'FreeBSD: { url: "pkg+https://pkg.FreeBSD.org/${ABI}/latest=E2=80=9D=
}=E2=80=99 > /usr/local/etc/pkg/repos/FreeBSD.conf
3. pkg update -f
4. pkg upgrade postgresql16-server postgresql16-client (etc.)
5. (PostgreSQL=E2=80=99s usual db server update dance)
6. rm -f /usr/local/etc/pkg/repos/FreeBSD.conf
7. pkg update -f
But I=E2=80=99d be wary of the resulting mixture of packages possibly =
causing unforeseen and unnecessary problems. Caution is advised.
HTH!
> On Dec 3, 2024, at 5:32=E2=80=AFPM, fatty.merchandise677@aceecat.org =
wrote:
>=20
> On Tue, Dec 03, 2024 at 08:54:12AM +0100, Andrea Venturoli wrote:
>=20
>> Maybe the OP is using 2024Q4 port tree?
>=20
> Yes.
>=20
> I don't really want any churn other than security fixes. Is there
> a way to use mostly Q4 but make an exception for a particular package
> or even just a particular update? I guess I'd be fine with just
> downloading the package with curl and unpacking it manually, in this
> once case.
>=20
>> PostgreSQL updates are often not MFH (even for security fixes).
>=20
> Sorry, please explain MFH. I'm a recent arrival ;-)
>=20
> --=20
> Ian
>=20
--Apple-Mail=_F841E360-B03F-4903-93DF-85520A2D7E58
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=utf-8
<html><head><meta http-equiv=3D"content-type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"overflow-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;">MFH stands for =
=E2=80=9Cmerged from HEAD=E2=80=9D, which is FreeBSD parlance for =
merging some changeset from the HEAD of some Git branch, most usually =
=E2=80=9Cmain=E2=80=9D, into some other branch, in this case one of the =
ports quarterly branches.<div><br></div><div>This applies to the =
conversation at hand because, as you may know, FreeBSD offers binary =
packages either from a =E2=80=9Cquarterly=E2=80=9D repository, =
i.e.:</div><div><br></div><div>-> cat =
/etc/pkg/FreeBSD.conf </div><div>(=E2=80=A6)</div><div>FreeBSD: =
{</div><div> url: =
"pkg+https://pkg.FreeBSD.org/${ABI}/quarterly",</div><div> =
mirror_type: "srv",</div><div> signature_type: =
"fingerprints",</div><div> fingerprints: =
"/usr/share/keys/pkg",</div><div> enabled: =
yes</div><div>}</div><div><br></div><div>which is currently pulling from =
the ports tree=E2=80=99s 2024Q4 branch, or from a =E2=80=9Clatest=E2=80=9D=
repository, which always builds directly from the tip of the ports =
tree=E2=80=99s main branch (hence the name). At the tip of =
the <font color=3D"#000000">2024Q4 branch the PostgreSQL ports are =
currently at 16.4, and the bump to 16.6 hasn=E2=80=99t been =
=E2=80=9CMFH=E2=80=99d=E2=80=9D into 2024Q4; that is why no amount of =
=E2=80=9Cpkg update && pkg upgrade=E2=80=9D will ever show you =
any updates for those packages, at least not until an MFH occurs, if it =
does, or a new =E2=80=9Cquarterly=E2=80=9D branch is cut, e.g. 2025Q1 =
(whenever that happens), and the upstream builders switch the =
=E2=80=9Cquarterly=E2=80=9D repo to =
it.</font></div><div><br></div><div><div>As for how you=E2=80=99d =
install *only* the updated PostgreSQL packages from the latest =
repository, while keeping the rest of your system on quarterly, I guess =
that could be achieved by some combination =
of:</div><div><br></div><div>1. mkdir -pv =
/usr/local/etc/pkg/repos</div><div>2. echo 'FreeBSD: { url: <span =
style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, =
0);">"pkg+https://pkg.FreeBSD.org/${ABI}/latest</span><font =
color=3D"#000000"><span style=3D"caret-color: rgb(0, 0, =
0);">=E2=80=9D</span></font> }=E2=80=99 > =
/usr/local/etc/pkg/repos/FreeBSD.conf</div><div>3. pkg update =
-f</div><div>4. pkg upgrade postgresql16-server <span =
style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, =
0);">postgresql16-client (etc.)</span></div><div><font =
color=3D"#000000"><span style=3D"caret-color: rgb(0, 0, 0);">5. =
(PostgreSQL=E2=80=99s usual db server update =
dance)</span></font></div><div><span style=3D"caret-color: rgb(0, 0, 0); =
color: rgb(0, 0, 0);">6. rm -f </span><span style=3D"caret-color: =
rgb(0, 0, 0); color: rgb(0, 0, =
0);">/usr/local/etc/pkg/repos/FreeBSD.conf</span></div><div><font =
color=3D"#000000"><span style=3D"caret-color: rgb(0, 0, 0);">7. pkg =
update -f</span></font></div><div><font color=3D"#000000"><span =
style=3D"caret-color: rgb(0, 0, 0);"><br></span></font></div><div><font =
color=3D"#000000">But I=E2=80=99d be wary of the resulting mixture of =
packages possibly causing unforeseen and unnecessary problems. Caution =
is advised.</font></div><div><font =
color=3D"#000000"><br></font></div><div><font =
color=3D"#000000">HTH!</font></div><div><div><br><blockquote =
type=3D"cite"><div>On Dec 3, 2024, at 5:32=E2=80=AFPM, =
fatty.merchandise677@aceecat.org wrote:</div><br =
class=3D"Apple-interchange-newline"><div><div>On Tue, Dec 03, 2024 at =
08:54:12AM +0100, Andrea Venturoli wrote:<br><br><blockquote =
type=3D"cite">Maybe the OP is using 2024Q4 port =
tree?<br></blockquote><br>Yes.<br><br>I don't really want any churn =
other than security fixes. Is there<br>a way to use mostly Q4 but make =
an exception for a particular package<br>or even just a particular =
update? I guess I'd be fine with just<br>downloading the package with =
curl and unpacking it manually, in this<br>once case.<br><br><blockquote =
type=3D"cite">PostgreSQL updates are often not MFH (even for security =
fixes).<br></blockquote><br>Sorry, please explain MFH. I'm a recent =
arrival ;-)<br><br>-- =
<br>Ian<br><br></div></div></blockquote></div><br></div></div></body></htm=
l>=
--Apple-Mail=_F841E360-B03F-4903-93DF-85520A2D7E58--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B8BEA61A-2D54-41E1-B533-F5B553E6F5BC>